-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run bare rust CLI binary, no node #88
Comments
Note, https://github.com/swc-project/swc/releases/tag/v1.3.25 contains all of @realtimetodie fixes so we should be unblocked now. |
#57 has landed, thanks @realtimetodie |
Hi, I noticed that this changed removed the Is using rules_swc in a custom rule no longer supported, or is there some other cli tool exposed through rules_swc that I can use for a custom update: I think I'm able to get it working with |
@binoche9 I'm sorry. This is only a documentation error. The Bazel target was renamed to -> Lines 18 to 20 in ee7ca02
The reason is, that the Bazel rule implementation only uses the In the future, there will also be a Bazel |
Yeah I believe that should give me enough to work with for now. Thanks for the quick response! |
reopened since I think the doc fix wasn't right. |
Actually I'm still seeing |
It does look like we should maybe expose the |
It's slow to start a NodeJS process for every spawn of swc, and it's extra weight to send to remote execution service.
SWC has a binary codenamed "swcx" which is the bare Rust binary without the node binding. This should be suitable for use in Bazel.
#57 has some longstanding WIP for this, but it needs a sponsor to fund the rest of the work.
The text was updated successfully, but these errors were encountered: