-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid npm token #3833
Labels
Comments
I cleaned out everything I could think of and reinstalled from npm and now it works. ¯_(ツ)_/¯ |
|
This issue has been automatically locked. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Before opening, please confirm:
App Id
d2733jdcx4wny6
AWS Region
us-west-2
Amplify Hosting feature
Backend builds, Frontend builds
Frontend framework
Angular
Next.js version
13.4.19
Next.js router
App Router
Describe the bug
2023-11-28T16:11:39.304Z [WARNING]: npm ERR! code E401
2023-11-28T16:11:39.307Z [WARNING]: npm ERR! Unable to authenticate, your authentication token seems to be invalid.
npm ERR! To correct this please trying logging in again with:
npm ERR! npm login
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2023-11-28T16_11_18_458Z-debug-0.log
2023-11-28T16:11:39.328Z [ERROR]: !!! Build failed
2023-11-28T16:11:39.328Z [INFO]: Please read more about Amplify Hosting's support for SSR frameworks to find if your build failure is related to an unsupported feature: https://docs.aws.amazon.com/amplify/latest/userguide/amplify-ssr-framework-support.html. You may also find this troubleshooting guide useful: https://docs.aws.amazon.com/amplify/latest/userguide/troubleshooting-ssr-deployment.html
2023-11-28T16:11:39.329Z [ERROR]: !!! Non-Zero Exit Code detected
2023-11-28T16:11:39.329Z [INFO]: # Starting environment caching...
2023-11-28T16:11:39.329Z [INFO]: # Environment caching completed
Terminating logging...
Expected behavior
It should build
Reproduction steps
Try to build
Build Settings
No response
Log output
Additional information
No response
The text was updated successfully, but these errors were encountered: