Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Auto-installed Node.js in .vaadin should not take precedence over global by default
See original GitHub issueFlow downloads and installs Node.js into ~/.vaadin if it can’t find npm command globally (i.e., on PATH). After such auto-installation, Flow will subsequently prefer npm and node commands in ~/.vaadin, even if a global installation has been added later. This version of node is used both when Flow runs npm install (when vaadin.pnpm.enable=false) and when it launches webpack-dev-server.
This is contradictory to the auto-install logic (which prefers global) and should not be the default behaviour. Only if the require.home.node parameter is set to true (false by default) should the ~/.vaadin/node/node be forced.
Flow version: 6.0-SNAPSHOT (2021-01-22).
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The starter wizard project uses Node 15 / npm 7. npm 7 uses a different lock file version than earlier npm versions (npm 7 == lockfile v2, earlier == lockfile v1)
Now every time I do something, not sure what, node is installed into ~/.vaadin/node
After this happens, the starter wizard (Vaadin 19) project uses the old node version and creates a v1 lockfile instead of the v2.
Then I have to delete ~/.vaadin/node to make everything work again.
Then some operation installs node into ~/.vaadin/node and it repeats.
This ticket/PR has been released with platform 19.0.7. For prerelease versions, it will be included in its final version.