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
This is NOT related to #35
We're using ProGet with NPM connector, and it handles "+" (plus sign) in versions differently than npmjs repository.
"versions": {"16.13.0+4.12.20": ...
"versions": ... {"16.13.0": ...
As you can see, the original npmjs API removes +4.12.20. While ProGet leaves it.
+4.12.20
I have analyzed all 1 240 000 npm packages in our ProGet repository and this one is the only one that has "+" in the version number.
I understand that it's an issue with ProGet and not with this package, but they don't want to fix it.
The issue is being covered in more details here: forums.inedo.com/topic/2948/npm-connector-returns-plus-in-versions
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
This is NOT related to #35
We're using ProGet with NPM connector, and it handles "+" (plus sign) in versions differently than npmjs repository.
As you can see, the original npmjs API removes
+4.12.20.While ProGet leaves it.
I have analyzed all 1 240 000 npm packages in our ProGet repository and this one is the only one that has "+" in the version number.
I understand that it's an issue with ProGet and not with this package, but they don't want to fix it.
The issue is being covered in more details here: forums.inedo.com/topic/2948/npm-connector-returns-plus-in-versions
The text was updated successfully, but these errors were encountered: