-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Module cannot be found in the npm registry #1
Comments
Please can you give some additional info what you mean with module is no visible in the npm registry? When I run npm info @sapmentors/cds-scp-api@latest I will get the information of the npm registry. |
Here's what I have on my side: $ npm --version
6.14.8
$ npm info @sapmentors/cds-scp-api@latest
npm ERR! code E404
npm ERR! 404 '@sapmentors/cds-scp-api' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it
npm ERR! 404 (or use the name yourself!)
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! 404
npm ERR! 404 '@sapmentors/cds-scp-api@latest' 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
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url. And: |
Check out the section Installing a package in Setting up GitHub packages for NPM. @raeijpe whats the reason you haven't published to npmjs? Check out the action we use in cds-pg: .github/workflows |
Hi Gregor, I published it public manually, today, but I have to wait 24 hours. I add you as admin and maybe you can set up the workflow |
Just FYI, the module is still not visible on npmjs.com |
Hi, This module is still not visible on npmjs.com per today |
Still not available |
Here we go: https://www.npmjs.com/package/@sapmentors/cds-scp-api Hope someone can help to fix the not working test issue. |
This module is no visible in the npm registry:
'@sapmentors/cds-scp-api@latest' is not in the npm registry.
The text was updated successfully, but these errors were encountered: