If we are renaming and starting with a clean slate, it would be a good start to make the modules ending with ‘2’ replace the default modules. Put all uncurried functions that now end with U into a separate module so they don’t pollute the module.
I really like the idea of cleaning up the JS-specific libraries. However, Pervasives and some of the other core OCaml modules do provide real value in certain situations. For example, the Int64 module can be a decent replacement for BigInt if the browser target doesn’t yet support BigInt (looking at you, Safari!).
Of course, some of the OCaml modules don’t make that much sense in a JS runtime, but perhaps there is some middle ground here?
I definitely think starting with a clean slate and using this as an opportunity to clean up would be a great idea. With onboarding js devs as easily as possible being a key goal, naming should probably follow Js conventions where ever it makes sense.
I personally really like the name „Belt“.
You could still sell it as „a toolbelt providing you with the right tools for every job“
Also it is really nice to write - at least on a qwertz Keyboard.