Today I learned that GitLab silently drops published NPM packages due to a wrong package prefix, while yarn publish thinks it successfully published a package to GitLab’s integrated NPM package repository. The key to solve it, is to prefix your package with the exact value of $CI_PROJECT_ROOT_NAMESPACE. For example, when your package is hosted under https://git.shivering-isles.com/sheogorath/node-markdown-spellcheck, your package has to use @sheogorath as package prefix, otherwise GitLab will silently drop it.

I came across this while using the feature for the first time on my GitLab. To be fair, it’s documented in the instructions, but it still was confusing to me to have a successfully published package according to yarn, that never showed up anywhere.