Add link from legacy Js modules to their current Core equivalents.

[gaspard]

Having a clear warning that Core supersedes Js helps remove some confusion for newcomers. It also avoids people trying to understand code samples that use legacy features such as |>.

[vercel[bot]]

@gaspard is attempting to deploy a commit to the ReScript Association Team on Vercel.

A member of the Team first needs to authorize it.

[aspeddro]

@gaspard, thanks for the contribution!!

json files are generated by the document generator @recript/tools. I like the idea of ​​adding a deprecation message.

It's better to do this in next.js side, here

[fhammerschmidt]

@aspeddro would we not need to add the deprecation messages to the compiler sources themselves?

[aspeddro]

If when Core was added in the compiler and keeping Js for some time it makes sense to add @deprecated in the Js module. But since Core is now an independent package it doesn't make sense to add any @deprecated in Js.

In short, it depends on how the transition from Js to Core will be in the compiler

[jderochervlk]

The Js module docs are now legacy and can no longer be found on the site.