Describe the issue
While reviewing backend package configuration files, I noticed that several dependencies currently use loose semver ranges such as ^ and ~ instead of exact pinned versions.
Where I found this
Files:
package.json
apps/public-api/package.json
apps/dashboard-api/package.json
packages/common/package.json
To Reproduce
-
Open the repository package.json files
-
Review dependency version declarations
-
Observe that multiple dependencies use loose semver ranges such as:
Expected behavior
Critical dependencies should ideally use deterministic versioning where appropriate to reduce inconsistent installs across environments.
Impact
Loose dependency ranges may:
- introduce unexpected dependency updates
- create install inconsistencies between environments
- make debugging dependency-related issues harder over time
Proposed solution
I plan to:
- review currently used dependency ranges
- evaluate which backend dependencies should be pinned more strictly
- keep compatibility and existing lockfile behavior in mind
- avoid unnecessary package churn
ETA
I’ll investigate this further and try to raise a PR by tonight.
Describe the issue
While reviewing backend package configuration files, I noticed that several dependencies currently use loose semver ranges such as
^and~instead of exact pinned versions.Where I found this
Files:
To Reproduce
Open the repository package.json files
Review dependency version declarations
Observe that multiple dependencies use loose semver ranges such as:
^~Expected behavior
Critical dependencies should ideally use deterministic versioning where appropriate to reduce inconsistent installs across environments.
Impact
Loose dependency ranges may:
Proposed solution
I plan to:
ETA
I’ll investigate this further and try to raise a PR by tonight.