Open simonhaenisch opened 1 year ago
The package-lock.json resolves tarballs to internal artifactory.spotify.net links that can't be reached by the public, e.g.
package-lock.json
artifactory.spotify.net
https://github.com/spotify/web-api-examples/blob/fd309a497e3582c9f94acf22d638d30bc8e5f7a8/get_user_profile/package-lock.json#L17
This causes npm install to get stuck.
npm install
You should probably:
rm package-lock.json
npm_config_registry="https://registry.npmjs.org/" npm install
To regenerate the lock-file with usable tarball URLs (and to not potentially leak implementation details of your internal Artifactory setup to the public 🤓).
The
package-lock.jsonresolves tarballs to internalartifactory.spotify.netlinks that can't be reached by the public, e.g.https://github.com/spotify/web-api-examples/blob/fd309a497e3582c9f94acf22d638d30bc8e5f7a8/get_user_profile/package-lock.json#L17
This causes
npm installto get stuck.You should probably:
rm package-lock.jsonnpm_config_registry="https://registry.npmjs.org/" npm installTo regenerate the lock-file with usable tarball URLs (and to not potentially leak implementation details of your internal Artifactory setup to the public 🤓).