npm access tokens (you probably don't need one)
The Neumo Design System packages are public on npm. Installing any
@kofile/* package — components, tokens, the MCP server, the Figma toolkit —
needs no account and no token:
npm install @kofile/gds-react
This page used to walk through creating a read-only token, because the packages were private. They aren't any more, so there are only two reasons left to read it.
1. Installs fail with 401 because of an old token
If you set a token up while the packages were private, it is still in your
~/.npmrc. npm sends it with every request, public packages included, and when
the token expires or is revoked npm refuses the request with 401 Unauthorized — even though the package itself is public.
Remove it:
npm config delete //registry.npmjs.org/:_authToken
Then check:
npm view @kofile/gds-react version
A version number means you're fine.
| What you see | Likely cause | Fix |
|---|---|---|
npm error 401 Unauthorized on a @kofile/* package |
An old or expired token in ~/.npmrc |
npm config delete //registry.npmjs.org/:_authToken, then retry |
npm whoami says 401 |
Same — the token in ~/.npmrc is no longer valid |
Same fix. whoami failing is normal once the token is gone |
A project's own .npmrc has _authToken=${NPM_TOKEN} |
Left over from when the packages were private | Delete that line from the project's .npmrc |
npm error 404 Not Found on a @kofile/* package |
A typo in the package name, or a version that was never published | Check the name with npm view @kofile/<name> |
2. You publish the packages
Publishing is the one thing that still needs npm credentials: membership of the
@kofile npm organization with publish rights, and a one-time password from
your authenticator for every publish. That's maintainers only, and it's covered
in RELEASE.md.
Contributors don't publish.
Security: if you do have a publish token, treat it like a password. It lives in your private
~/.npmrc; never paste it into a shared file, a repo, or a screenshot.