We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
opam
We can make npm-opam support both forms until esy becomes the standard.
npm-opam
esy
https://github.com/yunxing/opam-npm
We should also consider having better documentation for how people can convert their own packages.
The text was updated successfully, but these errors were encountered:
Currently at https://github.com/esy-ocaml/esy-opam
There are a couple of changes:
@opam-alpha
Sorry, something went wrong.
We publish packages to a custom registry (rather than to GitHub repos and npm proxy packages within the package scope, like @opam-alpha).
Is there a reason why this is better than a git repo? I did not find a significant performance difference.
We specify concrete versions of OPAM packages which we need to convert (rather than the number of latest releases).
Great!
Closing this as we integrated opam packages installation into esy install command.
esy install
No branches or pull requests
We can make
npm-opam
support both forms untilesy
becomes the standard.https://github.com/yunxing/opam-npm
We should also consider having better documentation for how people can convert their own packages.
The text was updated successfully, but these errors were encountered: