Currently facing a perplexing dilemma with no clear solution in sight.
In our ongoing project, we rely on npm for package management. Although we haven't been utilizing package-lock.json file lately, the need to reintroduce it has emerged.
The issue lies with the custom packages (e.g., "my-components") that we install through npm containing our components code. It is imperative that these packages always fetch the latest version during an "npm install".
Is there a way to exclude specific packages from being locked in the package-lock.json? Or perhaps there's an alternative solution to this predicament?
Our desired scenario entails locking all packages, except for our custom ones, to a particular version while ensuring the custom packages are always installed using the latest version.
EDIT: To further elaborate, our primary struggle arises from not pulling precise versions of our custom packages during development. Instead, we simply retrieve whatever resides on the #dev branch. We have version numbers set for specific releases, which works well. The ultimate goal is to have our custom packages designated as "Always pull content from the dev branch whenever 'npm install' is executed," while still maintaining specific version locks on all other packages.