Support omit-lockfile-registry-resolved from NPM configuration

[tinovyatkin]

What is the problem this feature would solve?

Our team uses a private NPM repository proxy with a dynamically generated URL that varies across developer machines and CI environments. Currently, including the full registry URL in the lockfile makes it unsuitable for sharing through a Git repository. NPM addresses this issue with the omit-lockfile-registry-resolved option, which works perfectly in our case by excluding registry-specific URLs from the lockfile.

What is the feature you are proposing to solve the problem?

We propose that bun supports the omit-lockfile-registry-resolved option and allows it to be imported from .npmrc. This enhancement would align Bun with NPM’s functionality and improve its usability in environments like ours, where lockfile portability is essential.

What alternatives have you considered?

We are currently exploring the option of disabling the lockfile entirely through bunfig.toml. However, this approach negatively impacts the reproducibility of our builds, making it less than ideal for our use case.