-
Notifications
You must be signed in to change notification settings - Fork 161
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
npm/pnpm install does not show version conflicts #13285
Comments
There should be in the logs the warning level message In development mode this might get lost in the logs as it is run in the dev thread. Project code should always be scanned first so the annotations from it should override any packages defined in any add-ons or components. |
So this is an issue with development mode as there we do not have the duplicate check. |
If encountering multiple NpmPackage annotations with different versions log a warning and inform of choice taken. Fixes #13285
If encountering multiple NpmPackage annotations with different versions log a warning and inform of choice taken. Fixes #13285
If encountering multiple NpmPackage annotations with different versions log a warning and inform of choice taken. Fixes #13285
If encountering multiple NpmPackage annotations with different versions log a warning and inform of choice taken. Fixes #13285
If encountering multiple NpmPackage annotations with different versions log a warning and inform of choice taken. Fixes #13285
This ticket/PR has been released with Vaadin 14.8.6. |
This ticket/PR has been released with Vaadin 23.0.3. |
Description of the bug
We have a large application, that defines npm packages using the flow annotation. We had now the case, that (p)npm install had run all the time despite there have been no changes to the npm packages. After some research we found, that there have been two different versions of the same npm package.
While in earlier Vaadin versions npm install had shown warnings for conflicting versions, now it does not anymore neither with npm nor with pnpm.
Expected behavior
Using (p)npm install should show version conflicts.
Minimal reproducible example
@NpmPackage(value = "tippy.js", version = "6.3.5")
on one and@NpmPackage(value = "tippy.js", version = "6.3.7")
on the secondStep 5 might seem a bit theoretical, but as Vaadin seem to use the "last" found version, this is necessary to show, how the version seems to be picked randomly from addons / other modules.
Versions
The text was updated successfully, but these errors were encountered: