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.

Sign up for GitHub

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

Jump to bottom

Should the plugin leverage opam formulas for `npm-version` constraints? #4

Open

jchavarri opened this issue Aug 10, 2023 · 0 comments

Member

jchavarri commented Aug 10, 2023

The plugin could leverage opam formulas to constraint the versions of the packages. For example, rather than writing:

{npm-version = "^16.0.2"}

One could write:

{npm-version >= "16.0.2" & npm-version < "17.0.0"}

This would allow removing the vendored esy code, but on the other hand might be less convenient.

@davesnx @anmonteiro wdyt?

The text was updated successfully, but these errors were encountered:

jchavarri mentioned this issue

Constraint checks #2

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment