Replies: 3 comments
-
It was working as of 0beae2e As time has gone on, dependencies have changed and this project is no longer actively maintained. |
Beta Was this translation helpful? Give feedback.
0 replies
-
How can we keep it alive? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks for asking.
Given the tool's status internally (still in use and maintained but not in
active development) and the difficulty we've had keeping the internal and
external versions in sync, I think we'd be OK with the external version
diverging, especially if it gets fixed. I'll be happy to approve PRs that
fix it, and would also be happy to add a link to a fixed fork.
…On Fri, Aug 11, 2023 at 12:45 PM glytchninja ***@***.***> wrote:
How can we keep it alive?
—
Reply to this email directly, view it on GitHub
<#53 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA27XB5EASGIPOKFSWUKEITXU2DT5ANCNFSM6AAAAAAUYIXS4A>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I'm trying to get this running in Ubuntu 22.04, following the instructions for yarn and nodejs. I will admit I use bazel/node very little. Seems like I need nodejs >= 14, so I already have to use a different package source (which is fine). Should I use 16? 18? Which is the most tested version with this project?
Additionally, is there a particularly stable commit or release I should try?
Currently, I get lots of different errors trying to run, so before I report them, I'd like to start at "known stable"
Beta Was this translation helpful? Give feedback.
All reactions