Is your feature request related to a problem? Please describe.
Currently node package versions inside the package.json are only fixed to the minor versions. However I think we could pin it to the patch version level. This matches the behaviour we have in Java based projects with the pom.xml. Pinned versions prevent side effects by unexpected version bumps at patch level. Even at patch level things can break.
It's our job to provide a functional and stable template. That's why I would pin it.
Using tools like Renovate bot makes LCM at patch level a breeze.
Describe the solution you'd like
Pinning version of dependencies and devDependencies inside node-based projects (package.json)
Is your feature request related to a problem? Please describe. Currently node package versions inside the package.json are only fixed to the minor versions. However I think we could pin it to the patch version level. This matches the behaviour we have in Java based projects with the pom.xml. Pinned versions prevent side effects by unexpected version bumps at patch level. Even at patch level things can break. It's our job to provide a functional and stable template. That's why I would pin it. Using tools like Renovate bot makes LCM at patch level a breeze.
Describe the solution you'd like Pinning version of dependencies and devDependencies inside node-based projects (
package.json
)Describe alternatives you've considered
Additional context