Skip to content
New issue

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

Push opam converter to Yunxing's npm-opam #33

Closed
jordwalke opened this issue Jan 9, 2017 · 3 comments
Closed

Push opam converter to Yunxing's npm-opam #33

jordwalke opened this issue Jan 9, 2017 · 3 comments

Comments

@jordwalke
Copy link
Owner

We can make npm-opam support both forms until esy becomes the standard.

https://github.com/yunxing/opam-npm

We should also consider having better documentation for how people can convert their own packages.

@jordwalke jordwalke added this to the 0.0.1 — First Release milestone Jan 9, 2017
@andreypopp
Copy link
Collaborator

Currently at https://github.com/esy-ocaml/esy-opam

There are a couple of changes:

  • We publish packages to a custom registry (rather than to GitHub repos and npm proxy packages within the package scope, like @opam-alpha).
  • We specify concrete versions of OPAM packages which we need to convert (rather than the number of latest releases).

@jordwalke
Copy link
Owner Author

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!

@andreypopp
Copy link
Collaborator

Closing this as we integrated opam packages installation into esy install command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants