A modern programming language that makes developers happier.

kotlinlang

<@UL1A5BA2X> Has there been any changes in the npm publish plugin that would lead to publication errors??

for some reasons my CI has started throwing authentication errors. Is this something to do with npm publish plugin or npm itself?

We do publish to a private vedaccio npm registry

Nothing in auth domain. Can you share some error logs?

```&gt; Task :pimonitor-api-public-core:publishJsNpmPublicationToAndylamax FAILED
npm notice 
npm notice 📦  @picortex/monitor-api@0.0.66
npm notice === Tarball Contents === 

. . .

npm notice 296B    package.json                                                       
npm notice 113.7kB pimonitor-api.d.ts                                                 
npm notice 17.8kB  pimonitor-api.js                                                   
npm notice 564B    pimonitor-api.js.map                                               
npm notice === Tarball Details === 
npm notice name:          @picortex/monitor-api                   
npm notice version:       0.0.66                                  
npm notice filename:      @picortex/monitor-api-0.0.66.tgz        
npm notice package size:  774.6 kB                                
npm notice unpacked size: 4.9 MB                                  
npm notice shasum:        1d640c7f74d7412482c70c44fded09dba5c8b9d4
npm notice integrity:     sha512-hD7eYOopzbTFj[...]7TWFFB3NuSk5g==
npm notice total files:   139                                     
npm notice 
npm ERR! code ENEEDAUTH
npm ERR! need auth This command requires you to be logged in.
npm ERR! need auth You need to authorize this machine using `npm adduser`

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/andylamax/.npm/_logs/2022-02-21T14_14_23_073Z-debug.log```

For others experiencing this in the future - the issue was caused by upgraded kotlin plugin version which in itself upgraded to a newer node/npm version. All of this resulted in lost support for empty `authToken` when publishing to repos without authorisation. The fix - put any non-empty string into `authToken`.