npm run bootstrap fails

[zom-bee]

npm ERR! 404 Not Found - GET https://registry.npmjs.org/@wmfs%2fgazetteer-blueprint - Not found

[siroje]

I too get this error.

Steps to reproduce.

• npm install -g lerna
• npm run sync
• npm run bootstrap

error

lerna ERR! npm install --global-style exited 1 in '@wmfs/addressbase-premium-blueprint'
lerna ERR! npm install --global-style stderr:
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@wmfs%2fgazetteer-blueprint - Not found
npm ERR! 404
npm ERR! 404 '@wmfs/gazetteer-blueprint@1.30.1' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'addressbase-premium-blueprint'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/siroje/.npm/_logs/2021-02-25T10_06_45_180Z-debug.log

I can't find the @wmfs/gazetteer-blueprint package on npm - https://www.npmjs.com/package/gazetteer-blueprint or
https://www.npmjs.com/package/@wmfs/gazetteer-blueprint but this is package page asks to login.

Is the @wmfs/gazetteer-blueprint package published privately? Should it be public? Thanks!

[reecebrend]

Hi @zom-bee, @siroje thanks for bringing this to our attention. This is happening because, as the error messages state, that blueprint in particular is private.

Our solution here is to separate out all of the sensitive business information, and place that in a "mod" for the blueprint. This will mean we can convert the gazetteer-blueprint into a public repo and that will solve the issue.

We have now added a user story to our backlog.