Npm run release gives proper output but the npm package doesn't get created

commented 3 years ago

I may be just missing something simple. npm publish alone gives same result. Can anybody take a look?

The source:

The output:

Counting objects: 5, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 652 bytes | 0 bytes/s, done.
Total 5 (delta 2), reused 0 (delta 0)
remote: Resolving deltas: 100% (2/2), completed with 2 local objects.
   d921ac8..a8c1682  master -> master
 * [new tag]         v0.0.2 -> v0.0.2
npm notice 
npm notice ๐Ÿ“ฆ  [email protected]
npm notice === Tarball Contents === 
npm notice 1.4kB  package.json               
npm notice 188B               
npm notice 1.1kB  LICENSE                    
npm notice 11.0kB                  
npm notice 1.8kB  lib/module.js              
npm notice 382B   lib/templates/auth.js      
npm notice 0      lib/templates/feathers.js  
npm notice 269B   lib/templates/middleware.js
npm notice 3.6kB  lib/templates/plugin.js    
npm notice 127B   lib/templates/service.js   
npm notice 244B   lib/templates/store.js     
npm notice 863B   lib/templates/verbose.js   
npm notice === Tarball Details === 
npm notice name:          nuxt-feathers-vuex                      
npm notice version:       0.0.2                                   
npm notice package size:  7.0 kB                                  
npm notice unpacked size: 20.9 kB                                 
npm notice shasum:        f86f6db1c2549551b06ee7ea4eab744f972d1d45
npm notice integrity:     sha512-u7MhtuYXWPrpE[...]ukHP3fVGc5WVA==
npm notice total files:   12                                      
npm notice 
+ [email protected]0.0.2

The result: no such package exists

commented 3 years ago

Turned out the problem was with npm registry settings, it can be closed.

Question โ€ข Resolved
#c2 - Created 3 years ago