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
The webpack inner semver function computed result is different from the npm package semver , and the webpack inner function result seems not right.
What is the current behavior?
Running the function satisfy from semver and parseRange results in a possible bug. Specifically:
satisfy(parseRange('~1'), '1.2.3') === false
What is the expected behavior?
satisfy(parseRange('~1'), '1.2.3') === true
Other relevant information: the result is not the same with semver
const semver = require('semver'); semver.satisfies('1.2.3','~1') === true
The text was updated successfully, but these errors were encountered:
I added a reproduction repository
https://github.com/2heal1/webpack-demo
Running test by the follow steps:
npm i
npm run test-special-tilde
npm run test-special-x-range
Sorry, something went wrong.
@2heal1 Sounds like a bug, do you want to send a PR?
@alexander-akait hey is the issue still open? can i try it ?
Yes, feel free to send a PR
snitin315
Successfully merging a pull request may close this issue.
Bug report
The webpack inner semver function computed result is different from the npm package semver , and the webpack inner function result seems not right.
What is the current behavior?
Running the function satisfy from semver and parseRange results in a possible bug. Specifically:
What is the expected behavior?
Other relevant information:
the result is not the same with semver
The text was updated successfully, but these errors were encountered: