Not working template jira-custom-field-custom-ui

Forge
, , ,
1

I’m trying to test templates of forge, and I tried to run the jira-custom-field-custom-ui template.

Just created it and then tried to run npm install inside of the static project and it failed with below error.

npm verb stack HttpErrorAuthUnknown: Unable to authenticate, need: Basic
npm verb stack     at /Users/omerfarukak/.nvm/versions/node/v20.10.0/lib/node_modules/npm/node_modules/npm-registry-fetch/lib/check-response.js:80:17
npm verb stack     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
npm verb statusCode 401
npm verb pkgid yaml@https://packages.atlassian.com/api/npm/npm-remote/yaml/-/yaml-1.10.2.tgz
npm verb cwd /Users/omerfarukak/forge-test/static/hello-world
npm verb Darwin 21.6.0
npm verb node v20.10.0
npm verb npm  v10.2.5
npm ERR! code E401
npm ERR! Incorrect or missing password.
npm ERR! If you were trying to login, change your password, create an
npm ERR! authentication token or enable two-factor authentication then
npm ERR! that means you likely typed your password in incorrectly.
npm ERR! Please try again, or recover your password at:
npm ERR!     https://www.npmjs.com/forgot
npm ERR! 
npm ERR! If you were doing some other operation then your saved credentials are
npm ERR! probably out of date. To correct this please try logging in again with:
npm ERR!     npm login
npm verb exit 1

Looks like these templates only can be used internally, not from customers like us.

2

You should be able to remove the yarn.lock or package.lock and try again; looks like a package that is available publicly too. But it is a mistake that this ships with that registry.

3

hi @rmassaioli,
removing package.lock didn’t help, this project was fresh and so it shouldn’t be a problem, and I use the latest LTS of node. But yarn install helped to install, thanks!

4

Hi @masterkeylog,

This was a bug in our template packaging. It’s now fixed, and if you use forge create again you shouldn’t have this problem.

If you’d like to keep your existing project, please remove package-lock.json from the static project and run npm install or yarn install again.

Also make sure you are using npm or yarn consistently - they will both create their own lock files (package-lock.json or yarn.lock) and having both can cause confusion for yourself and your fellow developers.