Storing the resolutions for yarn link'd modules outside of package.json?

[Makeshift]

When developing, you often have multiple projects that have dependencies between them. Sometimes it isn't viable to have them all be part of a yarn workspace, so the accepted way of handling local development between non-workspace projects seems to be to use yarn link.

However, this adds the resolution directly to package.json, which the developer then needs to remember to remove before commiting (because it isn't relevant to anyone else):

  "resolutions": {
    "my-other-project": "portal:/home/connor/repos/...",
  }

I'm awful at remembering to remove them, so I often accidentally commit the resolution, which of course makes CI fail so it isn't a danger, but it's slightly inconvenient.

The ideal solution for me would be to have something along the lines of package.local.json which could be excluded from git, but I'm sure I'm not the only person with this issue and there is a better solution.

Is there a better way of handling this? What do other devs do?