-
Notifications
You must be signed in to change notification settings - Fork 135
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
Publish to npm? #851
Comments
I thought this was going to be about publishing the wasm build! No strong opinion. I don't think I'd use that myself but sure, go ahead. |
There is already quickjs-emscripten which is more comprehensive IMHO. I'll leave this open and think about it some more :-) |
I've been trying to find a way to use C/Rust command line tools in JS recently. Although it's still in the early stages, there is a qjs example for testing. This is more portable than wasm and napi. |
This is very close to what I was thinking! If you intend to maintain it I'd be happy to have a link to it in the documentation! |
This is just an executable file that downloads the corresponding platform from github, and then forwards the cli parameters, so there is not much maintenance work. only need to modify the version every time quickjs-ng is released. However, I can only release @easy-install/qjs instead of @quickjs-ng/qjs |
You can publish it under your org and update the docs to offer it as an option. Then we can see how it goes and condier moving it to this org. What do you think? |
Let's wait for some time while I do some testing and optimization and see if there is a better way. |
esbuild
is written in go but since it relates to the JS ecosystem it's also published to npm. One can simply donpx esbuild
and It Works (TM).At some point in time I snatched the
@quickjs-ng
npm org, so we could do something like:npx @quickjs-ng/qjs
and get the CLI ornpx @quickjs-ng/qjsc
to get the compiler.Thoughts?
The text was updated successfully, but these errors were encountered: