I have chosen to use Verdaccio as the platform for hosting a private package. In my current project, I am looking to incorporate this package locally. The package has been successfully published and is now hosted on Verdaccio running on localhost (http://localhost:4873)
However, I am encountering difficulties with jspm locating this package when executing jspm install. Despite incrementing the version number of the package during publishing on Verdaccio and updating the same version in the package.json file of my local project, I am facing issues. My ~/.npmrc file contains:
registry=https://npm.123-456.io
@myScope:registry=http://localhost:4873
I attempted to utilize scoping by adding it here. To add packages, I am using jspm install. Within my package.json, I have specified:
.
.
.
.
"jspm": {
"directories": {
"baseURL": "src",
"test": "test"
},
"configFile": "src/system.config.js",
"dependencies": {
"myPackage": "npm:@myScope/<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="711c082110121a10161431405f435f42">[email protected]</a>",
.
.
.
}
}
While running
npm install <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="fe9387ae9f9d959f999bbecfd0ccd0cd">[email protected]</a>jspm install generates the following error message:
err Repo npm:@myScope/myPackage not found!
Do I really need to implement scoping in this scenario? How can I ensure that jspm install effectively locates my package stored on Verdaccio?