Skip to content

[DX] Loose dependency version ranges may cause non-deterministic installs #210

@udaycodespace

Description

@udaycodespace

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

  1. Open the repository package.json files

  2. Review dependency version declarations

  3. 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.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions