Ruy Adorno

[Feedback](https://github.com/npm/rfcs/blob/c8cb6fe56ca8c7fc3dad5dd26f057aee472dc837/meetings/2020-10-21.md#pr-121-rfc-added-proposal-for-package-version-linkversioncomment-syntax---kael-shipman) from the last [OpenRFC call](https://youtu.be/MexcBT5vp14): - Adding new syntax to `package.json` is something we rather avoid since it creates all sorts of incompatibility problems among different package managers and...

Thanks @kael-shipman for bringing this one up 😊 we'll probably continue the conversation next week in the next OpenRFC call.

@iansu I do have a very hacky workaround that I've been using that works when you don't need that same dependency as a root dep, basically I declare an aliased...

discussion started here: https://github.com/npm/npm-packlist/issues/48 and the @npm/cli-team decided it would be nice to throw a proper RFC to discuss this a bit more with the community.

Action items from the [OpenRFC call](https://github.com/npm/rfcs/issues/122): - Restrict this RFC to only items that can be potentially harmful to the ecosystem (high potential of leaking secrets, etc) - Let's create...

It would be awesome if folks can contribute to this by suggesting files that they notice have high potential to be harmful if published by mistake to the registry 😊

from @bnb in OpenRFC call: > We could borrow items from: https://github.com/github/gitignore/blob/master/Node.gitignore

@jsg2021 yeah most definitely there were lots of discussions during the meetings. Long story short, this spawned a larger conversation about revamping the workspaces install algorithm and we're looking to...

in case we use a template system, it should probably also contain a value for version e.g: `[$workspaceName] v$workspaceVersion` in your original example @ljharb

good point @wraithgar I believe you're right, in case it's a prefix, it should just end at the **v**