Skip to content

Separated npm package for bucklescript dependencies #2769

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

Closed
snird opened this issue Apr 24, 2018 · 2 comments
Closed

Separated npm package for bucklescript dependencies #2769

snird opened this issue Apr 24, 2018 · 2 comments

Comments

@snird
Copy link

snird commented Apr 24, 2018

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..

@yawaramin
Copy link
Contributor

Seems to be duplicate of #2127

@bobzhang
Copy link
Member

bobzhang commented Feb 2, 2021

It is a long awaited feature request. Landed in master.
User can add a field in next release:

"external-stdlib" : "@rescript/std"

@bobzhang bobzhang closed this as completed Feb 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants