-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
yarn resolves incorrectly the datatables.net package vs npm #4176
Comments
I can confirm the same issue on CentOS 7 with NodeJS RPM from nodesource.com and yarn RPM from yarnpkg.com. |
More info:
The latest match for
In other words, after Yarn install we get:
NPM on the other hand seems to identify that
|
It's not a bug per-se, cf my comment here for the detailed explanation. TL;DR: |
@rally25rs @arcanis - may be we should have a canned answer or dedicated label for these. Also, I think we may do a better job when hoisting to prevent these a bit. |
It seems that in some cases, using this package end up pulling a wrong version of DataTables, this change prevent that. see yarnpkg/yarn#4176 for more info / backgroud. Thanks!
What is the current behavior?
yarn installs the wrong version of datatables.net
If the current behavior is a bug, please provide the steps to reproduce.
based on the following package.json
yarns pulls 'https://registry.npmjs.org/datatables.net/-/datatables.net-2.1.1.tgz vs npm that fetches 1.10.15.
yarn info datatables.net
npm info datatables.net
What is the expected behavior?
since the newer version of datatables was released incorrectly, I would really like to get the correct version using yarn :)
Please mention your node.js, yarn and operating system version.
node - v6.11.2
yarn - v0.27.5
OS - confirmed on fedora and rhel
Thanks!
The text was updated successfully, but these errors were encountered: