Morrison Cole

Hi @bmulholland - thanks for raising this (and for including the detail). Sounds like a problem with this action indeed! Will take a look later this week 🙏

> [@MorrisonCole](https://github.com/MorrisonCole) just wondering, why didn't you use the latest Yarn version instead of v3.5? > > Can you provide full repro scripts to run to be able to reproduce...

I'm seeing this too with `nodeLinker: node-modules` in a large monorepo when upgrading from `4.2.2` -> `4.8.0` (self hosted GH runners). Edit: doesn't occur for me on `4.7.0`. Will provide...

Hey @arcanis - thanks for taking a look so quickly! Can confirm that we don't see the issue with #6743 🎉

Here's the compare for anyone landing on this issue: https://github.com/iamhosseindhv/notistack/compare/v3.0.1...v3.0.2

I'd love to see this - definitely something missing from the eslint ecosystem at the moment! https://eslint.org/docs/latest/rules/no-restricted-imports#rule-details might be a good reference too, since it does something similar. Some granularity...

>This raises a good point about the value of a new rule for this. If the usage sites of a restricted package are being reported using no-restricted-imports what additional value...

Also the latest release is `2.0.5` but the main branch is still `2.0.4`... https://github.com/staylor/react-helmet-async/blob/main/package.json#L3