-
Notifications
You must be signed in to change notification settings - Fork 101
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
Providing nodeExecCommand
setting
#427
Comments
This is something that can be done with a custom import org.scalajs.jsenv.nodejs.NodeJSEnv
jsEnv := {
new NodeJSEnv(NodeJSEnv.Config()
.withExecutable("nvs")
.withArgs(List("exec", ver)))
} |
When suggesting this I mainly had interactions with Webpack in mind:
|
Wouldn't that be possible to do in user space using #420, then? |
No, because that PR does not expose these bundler related |
This is somewhat related to #418 - instead of directly supporting some node version manager, we could expose a setting that would allow users to set a
node
executable, similar to howsbt-native-packager
does it with dockerExecCommand. Then users ofscalajs-bundler
could wire in for example https://github.com/jasongin/nvs by settingnodeExecCommand
tonvs exec <ver>
.How does this sound @sjrd?
The text was updated successfully, but these errors were encountered: