You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I currently have an issue with npm install the bs-platform package in my production environment.
That is the the issue with the make error:
Error: Command failed: make world && make install
at checkExecSyncError (child_process.js:601:13)
at Object.execSync (child_process.js:641:13)
Which made me think, why do I need the compiler and the entire platform on my production environment?
I just need the js files that are dependencies for the compiled code.
I think it is a reasonable suggestion, to divide the packages.
So that for process that precompiles the code, we can have in dependencies just the js libraries, and in dev-dependencies have the compiler itself.
I don't know if my use case is wide enough, and couldn't find common examples for compilers that add their own js libraries as for what those are doing..
The text was updated successfully, but these errors were encountered:
I currently have an issue with
npm install
thebs-platform
package in my production environment.That is the the issue with the make error:
Which made me think, why do I need the compiler and the entire platform on my production environment?
I just need the js files that are dependencies for the compiled code.
I think it is a reasonable suggestion, to divide the packages.
So that for process that precompiles the code, we can have in
dependencies
just the js libraries, and indev-dependencies
have the compiler itself.I don't know if my use case is wide enough, and couldn't find common examples for compilers that add their own js libraries as for what those are doing..
The text was updated successfully, but these errors were encountered: