@falcowoski/semantic-release-npm-rename-package
Advanced tools
The classic and reliable @semantic-release/npm plugin, but with the ability to rename the package before publishing
The classic and reliable @semantic-release/npm plugin, but with the ability to rename the package before publishing ⚡️
npm install @falcowoski/semantic-release-npm-rename-package -D
pnpm add @falcowoski/semantic-release-npm-rename-package -D
This plugin is simply a wrapper around the original plugin, so all the original parameters are kept and we now have the new packageName optional parameter 🚀
One use case for this plugin is publishing the same package under multiple scopes or across multiple organizations 🏢
FAQs
The classic and reliable @semantic-release/npm plugin, but with the ability to rename the package before publishing
The npm package @falcowoski/semantic-release-npm-rename-package receives a total of 821 weekly downloads. As such, @falcowoski/semantic-release-npm-rename-package popularity was classified as not popular.
We found that @falcowoski/semantic-release-npm-rename-package demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Application Security
/Research
/Security News
Socket.dev found compromised various CrowdStrike npm packages, continuing the "Shai-Halud" supply-chain attack that previously hit `tinycolor`.
Research
/Security News
Malicious update to @ctrl/tinycolor on npm is part of a supply-chain attack hitting 40+ packages across maintainers
Security News
pnpm's new minimumReleaseAge setting delays package updates to prevent supply chain attacks, with other tools like Taze and NCU following suit.