Release candidate doesn't contain any file

[lukadriel7]

I'm having an issue:

After installing peer@rc, the folder only contains License, package.json and README.MD This seems to affect rc 5 and 6, I was able to install rc 4 and it isn't empty

[jonasgloning]

Thanks, @lukadriel7! You’re right; the package is empty on npm. Interestingly, that does not happen when building locally:

➜  npm pack
npm notice 
npm notice 📦  peer@1.0.0-rc.6
npm notice === Tarball Contents === 
npm notice 1.1kB  LICENSE               
npm notice 9.3kB  README.md             
npm notice 12.1kB dist/bin/peerjs.js    
npm notice 46.3kB dist/bin/peerjs.js.map
npm notice 20.8kB dist/index.js         
npm notice 38.9kB dist/index.js.map     
npm notice 20.3kB dist/module.js        
npm notice 38.9kB dist/module.js.map    
npm notice 2.0kB  dist/peer.d.ts        
npm notice 4.6kB  dist/peer.d.ts.map    
npm notice 2.4kB  package.json          
npm notice === Tarball Details ===

[github-actions[bot]]

:tada: This issue has been resolved in version 1.0.0-rc.8 :tada:

The release is available on:

• npm package (@rc dist-tag)
• GitHub release
• v1.0.0-rc.8

Your semantic-release bot :package::rocket:

[github-actions[bot]]

:tada: This issue has been resolved in version 1.1.0-rc.1 :tada:

The release is available on:

• npm package (@rc dist-tag)
• GitHub release
• v1.1.0-rc.1

Your semantic-release bot :package::rocket: