Would it make sense to have an updatePolicy field for package.json?

[castarco]

Hi, some time ago I submited a "pre-proposal" to NPM's RFCs repository ( npm/rfcs#703 ), based on an article I wrote about the same idea ( https://blog.coderspirit.xyz/blog/2023/06/29/beyond-semantic-versioning-updatepolicy/ ).

The basic idea is to provide more metadata to help package managers to make smarter decisions when managing direct and transient dependencies. In a way, it would be a more generic solution to the same problem that Yarn resolutions tries to fix.

There's no point on copying the same text I linked before in this same comment, but I'd love to have some feedback on the idea :) .

What do you think? Would it make sense to have an updatePolicy field supported by all package managers?

Note: I'm aware of the "Constraints" experimental feature, but this is not quite the same. It's more about declaring metadata about the package's versioning strategy (from both perspectives: producer and consumer).