-
Notifications
You must be signed in to change notification settings - Fork 425
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
Up to date reason npm package #2456
Comments
Now that I understand the vendoring process I can give more context: This apparently happened around 1 year ago I assume. |
@ryyppy this isn't true. You don't need bspack to produce refmt.js . Probably just lacks of man-power |
@thangngoc89 You mean refmt.js could be produced using a regular dune + jsoo setup? How would bucklescript compilation work? (side note: I always thought bspack was created originally because BS was a fork of OCaml and so could not be compiled with regular build tooling, but maybe that assumption is false and that's why I'm confused). cc @ulrikstrid as we've been discussing about bspack stuff lately :) |
@jchavarri refmt.js has been always produced by jsoo. Adding bspack into that is just noisy and more complexities for no reasons at all. bspack is for vendoring to bucklescript only |
So the answer to that is yes? |
Yes. refmt.js SHOULD be produce by a regular dune + jsoo setup |
We don’t release to NPM anymore |
The latest npm
reason
package version is3.3.4
which is over a years old. We want to use it for reformatting between Reason and OCaml syntax and would be great to have access to up to daterefmt
version. Is there any reason why the package is not updated with every new release?The text was updated successfully, but these errors were encountered: