npm 8.3.0 delivers the overrides feature, which can be used for locking dependency versions. However, when a user modifies the overrides section manually, Vaadin doesn't detect the change.
Edit package.json and add an override like "json-schema": ">=0.4.0"
Run mvn spring-boot:run
If the original npm installation used 0.3.0 like in my app, it will still use 0.3.0. This is only because
Skipping `npm install` because the frontend packages are already installed in the folder '.../node_modules' and the hash in the file '.../node_modules/.vaadin/vaadin.json' is the same as in 'package.json'
Expected behavior
Vaadin detects the changes in the overrides section.
Description of the bug
npm 8.3.0 delivers the overrides feature, which can be used for locking dependency versions. However, when a user modifies the overrides section manually, Vaadin doesn't detect the change.
Download a starter app from start.vadin
If the original npm installation used 0.3.0 like in my app, it will still use 0.3.0. This is only because
Expected behavior
Vaadin detects the changes in the overrides section.
Minimal reproducible example
Download a starter app from start.vadin
Versions