I would not want to be forced to use a package.json
, considering there are emerging tools that do not even rely on the package.json
I think within the JavaScript ecosystem there’s probably one concensus across all package managers and that’s the existence of a package.json
file (since it’s also what any package repository requires). So I’d be hard pressed to think of a package manager that deviates (or expect one to do so in the future).
As for the node_modules
workflow, I find it a better point of contention, though I don’t think it applies here.
As far as my understanding goes, the work being done here is mostly about how ReScript knows what modules it should look at to find ReScript code and which ones should be built.
There is an existing open compiler issue for support for things like yarn PnP
(which no longer uses node_modules
): https://github.com/rescript-lang/rescript-compiler/issues/3276 but I don’t think the changes being made here make that any more or less difficult.