You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
echo "One cause for node package install failure is if you have private repositories that it can't reach
26
+
One way to fix this for private npm packages:
27
+
1. Use the npm CLI's \"login\" command to create a token (usually saved in your user's \"~/.npmrc\" file)
28
+
For more info, see https://circleci.com/blog/publishing-npm-packages-using-circleci-2-0/#:~:text=set%20the%20%24npm_token%20environment%20variable%20in%20circleci
29
+
2. Add a NPM_TOKEN to an org context
30
+
For info on how to use contexts, see https://circleci.com/docs/contexts/
31
+
3. Add a .circleci/config.yml to your repository or use this config.yml as a starting template
32
+
4. Configure the jobs to use the context that includes NPM_TOKEN
33
+
5. Add a step to inject your NPM_TOKEN environment variable into npm before \"install-packages\"
34
+
For an example, see https://circleci.com/blog/publishing-npm-packages-using-circleci-2-0/#:~:text=the%20deploy%20job%20has%20several%20steps%20that%20run%20to%20authenticate%20with%20and%20publish%20to"
0 commit comments