Skip to content
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

js files get placed in src/, not in lib/js/src #15

Closed
SuperFluffy opened this issue Nov 13, 2018 · 2 comments
Closed

js files get placed in src/, not in lib/js/src #15

SuperFluffy opened this issue Nov 13, 2018 · 2 comments

Comments

@SuperFluffy
Copy link

SuperFluffy commented Nov 13, 2018

I have managed to get the examples running using both the native and the js backends. I am surprised, however, that bsb -make-world -native js places the resulting index.js not in lib/js/src/, as is expected by the index.html file, but puts it in src/.

In fact, I don't have lib/js/src, only a lib/bs/js/src, with the following contents:

% ls -1 lib/bs/js/src/
index.cmi
index.cmj
index.cmt
index.mlast
index.mlast.d
IndexHot.cmi
IndexHot.cmj
IndexHot.cmt
IndexHot.mlast
IndexHot.mlast.d

Why the discrepancy?

@SuperFluffy SuperFluffy changed the title js files get placed in src/, not in /lib/js/src js files get placed in src/, not in lib/js/src Nov 13, 2018
@bsansouci
Copy link
Owner

bsansouci commented Nov 13, 2018

There’s an option in bsconfig to in-line the generated is called “in-source”, see https://bucklescript.github.io/docs/en/build-configuration#package-specs

Do you have that option turned on?

@SuperFluffy
Copy link
Author

Thanks for the reply! Yes, indeed, that was it. It's a bsb -init . default, and I guessed that the behaviour should be the same between your more bare bsconfig.json and the generated one.

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

2 participants