exec
npm
Our great sponsors
exec | npm | |
---|---|---|
4 | 3 | |
123 | 232 | |
2.4% | 2.6% | |
7.0 | 9.0 | |
5 days ago | 1 day ago | |
JavaScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
exec
-
Semantic release to npm and/or ghcr without any tooling
@semantic-release/exec - used to set GitHub action environment variables when run as from docker container and GitHub action outputs when run as a marketplace action
-
Automatically update git major tags on GitHub marketplace release
This meant that forcing a major tag update with @semantic-release/exec as part of the release process was possible, but would result in the major tag (for example v3) linking to a valid repository commit SHA that is not actually released in the marketplace.
-
A complete guide to use dependabot with semantic-release and @vercel/ncc for GitHub Actions
This article introduces semantic-release as a solution. It automates the release process, and its exec plugin helps us to run @vercel/ncc before the release automatically.
-
You don’t need semantic-release (sometimes)
You may need a minor tweak up. For example, push some pkg to both public and internal registries. Ooops. "...publishing to two different registry is not a good idea". In this case you can not rely on stable, convenient and tested in millions runs semrel/npm plugin, and you have to just write a pair of commands by hand with semantic-release/exec instead:
npm
-
Using semantic-release to automate releases and changelogs
@semantic-release/npm to publish npm packages in a public or private registry
-
Automatically update git major tags on GitHub marketplace release
@semantic-release/npm
-
You don’t need semantic-release (sometimes)
You may need a minor tweak up. For example, push some pkg to both public and internal registries. Ooops. "...publishing to two different registry is not a good idea". In this case you can not rely on stable, convenient and tested in millions runs semrel/npm plugin, and you have to just write a pair of commands by hand with semantic-release/exec instead:
What are some alternatives?
Discord-Hide-Blocked-Messages - Ways to hide discords "1 blocked message - show message" buttons
semantic-release-monorepo-hooks - Workarounds to handle `semantic-release-monorepo` multipublishing
setup-buildx-action - GitHub Action to set up Docker Buildx
npmlog - The logger that npm uses
semantic-release - :package::rocket: Fully automated version management and package publishing
semantic-release-toolkit - Semantic release tools, plugins and configs for QIWI OSS projects
zx - A tool for writing better scripts
semantic-release-docker - semantic-release plugin to build and push docker images
Reg2CI - Create System Center Configuration manager ConfigItem (CI's) from a .reg (Registry) or a .pol (Policy) file.
semantic-release-gh-pages-plugin - github-pages publishing plugin for semantic-release