> I also suggest you fully commit to yarn or npm, they are definitely different enough to be awkward to combine. I can't even migrate to Yarn because of issues

> I also suggest you fully commit to yarn or npm, they are definitely different enough to be awkward to combine. I can't even migrate to Yarn because of issues. Try using a package that has binary (`bin` in `package.json`) or other metadata and publish on your private NPM registry and then use it with Yarn or NPM v7 you won't be able to as it strips away this metadata. For example, if I want to push a patched version of Playwright to my NPM registry. I can't use it if I don't use NPM v6. Also the daily 404s errors when trying to install your private NPM packages which requires retry your jobs isn't help either. Sadly it's not an important enough issue for them to fix. I am really wondering if Gitlab is using their products themselves.