For the next major release our plan is to sunset the rescript-legacy build system (internally named bsb) and completely replace it with the new build system announced in rescript 12.
If you are already using npx rescript on version 12, nothing will change for you. You are only impacted if you cannot use the new build system. If that’s the case, please let us know what blocks you from upgrading.
We have posted an analysis of potential gaps that Rewatch has with bsb. If you use any of the listed features, please speak up. It would be most convenient for us maintainers if we could simply remove the missing features, but of course we don’t want to do that without a broader conversation with the community.
I think you can already remove use-stdlib and external-stdlib from that list, both are leftovers.
use-stdlib is not implemented anymore even in bsb, and external-stdlib does not make any sense anymore now that the stdlib is always an external package @rescript/runtime.
Ok thanks! The only one we use is reanalyze but we don’t really use that, I’m totally confused on the state of reanalyze anyway.
We have yet to try out the new js-post-build which has been the only thing holding us back AFAIK but I will report back once I’ve tried switching to the new build system.
There has been a rewrite of reanalyze to be fully reactive and it should now be possible to use it in monorepos as well. We’ll release a blogpost about it as soon as the tooling/editor integration is fixed.
IMO the reanalyze field is here to stay, it just appeared in this list because rewatch itself does not do anything with it.