"401 Unauthorized" build error about srcery-terminal HOT 7 CLOSED

Hi, you need a package read token configured to be able to download github packages. More here: https://github.com/srcery-colors/srcery-palette

from srcery-terminal.

From this page https://github.com/srcery-colors/srcery-palette/pkgs/npm/srcery-palette, this command
npm install @srcery-colors/[email protected]
outputs

npm WARN config tmp This setting is no longer used.  npm stores temporary files in a special
npm WARN config location in the cache, and they are managed by
npm WARN config     [`cacache`](http://npm.im/cacache).
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@srcery-colors%2fsrcery-palette - Not found
npm ERR! 404
npm ERR! 404  '@srcery-colors/[email protected]' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

from srcery-terminal.

Just making sure:

1. you did create a read package token and added it to your personal npmrc?
2. in the example above, did you run the install command from project root?
   • If you didn't the registry is not configured. See https://github.com/srcery-colors/srcery-terminal/blob/master/.npmrc

from srcery-terminal.

This isn't that user friendly, its a result of publishing package on github packages, I thought it would be a bit more seamless than it turned out. This package was intended for internal development so I figured github packages was a good fit, but I strongly consider just adding it to the npm registry.

from srcery-terminal.

k, github packages cause issues with CI also, which I should've figured. I'll either setup a secret or push to npm, not sure yet

from srcery-terminal.

Alright, took me a while but install issues should be solved now, I've published the package on npm.
https://www.npmjs.com/package/@srcery-colors/srcery-palette
CI passes so you shouldn't have any issues installing anymore

from srcery-terminal.

It works now. Thanks!

from srcery-terminal.