Currently, the prerelease publishes npm package with tab "beta" and then when the release is published it attempt to publish the same version code but under the "latest" tag. NPM doesn't like this, essentially publishing the same version code more than once.
It's smarter to find a sophisticated work around, but it's faster to just going back to what works in the meantime :)
Currently, the prerelease publishes npm package with tab "beta" and then when the release is published it attempt to publish the same version code but under the "latest" tag. NPM doesn't like this, essentially publishing the same version code more than once.
It's smarter to find a sophisticated work around, but it's faster to just going back to what works in the meantime :)