conventional-changelog
execa
Our great sponsors
conventional-changelog | execa | |
---|---|---|
11 | 20 | |
7,574 | 6,349 | |
1.4% | - | |
9.0 | 9.6 | |
4 days ago | 6 days ago | |
TypeScript | JavaScript | |
ISC 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.
conventional-changelog
-
Using semantic-release to automate releases and changelogs
conventional-changelog-conventionalcommits is a package used for creating conventional commits and has a bit more configuration possibilities with changelogs in contrast to the default Angular commit scheme.
-
Conventional Commits - Specification for Your Commit Messages
Finally, it is also interesting to be able to automatically generate the CHANGELOG file from the commit messages. There are various tools for this, one of them is Conventional Changelog
-
Minor imperfections that shout ‘beginner code’
Some projects generate change logs automatically from commits. For example, angular uses conventional-changelog.
- GitHub Actions can't find built binaries to put them to a release
- FRONT END - LINKS CRIATIVOS E TÉCNICOS
-
Confused about how to get my packages up to `1.0.0` using Lerna / Conventional commits...
I'm under the understanding from this issue that in semver, a package that is <1.0.0 is considered unstable. This means that a breaking change can occur at any version, usually between minors.
-
Automatically update git major tags on GitHub marketplace release
conventional-changelog-conventionalcommits
-
Keep a Changelog
[1] - https://github.com/conventional-changelog/conventional-chang...
-
What are some good practices for writing changelogs/update notes?
I dont use myself, but some people follows something like the conventional commit spec, and then uses a generator.
-
Automated versioning and package publishing using GitHub Actions and semantic-release
@semantic-release/commit-analyzer It determines the type of our release (e.g. major, minor, patch) by analyzing commits with conventional-changelog. semantic-release uses Angular Commit Message Conventions by default.
execa
-
Google ZX – A tool for writing better scripts
I’m partial to Sindre Sorhus’ execa, this document outlines the differences:
https://github.com/sindresorhus/execa/blob/main/docs/scripts...
- Execa: Process Execution for Humans in Node.js
-
The Bun Shell
Yeah, or over https://github.com/sindresorhus/execa?
And given the existence of those npm packages, is there any aspect of Bun Shell that required it to be built into the Bun runtime instead of published to npm?
For something which works across all JS runtimes (Deno, Node) and achieves basically the same, check out the popular JS library Execa[1]. Works like a charm!
[1]: https://github.com/sindresorhus/execa
-
Building Reactive CLIs with Ink - React CLI library
To simplify the process of running the commands, I will use execa - abstraction library on top of Node.js child_process methods.
-
How to run DB migrations in CICD Pipeline
Hello, this is an interesting problem. At https://stacktape.com (where we're creating a developer-friendly abstraction of AWS), we're recommending 2 options: - use a "deployment script" (basically a custom-resource lambda function that runs during the CloudFormation deployment). You can install prisma into it, and then execute the migration command from the lambda function using something like execa, if you're using Javascript/Typescript. You can easily do this with Stacktape anytime. - use a bastion (EC2) instance (deployed to the the VPC where your RDS db is). The cheapest instances cost ~4.5$/month, so it shoudln't be too costly. You can also securely connect to it using EC2 instance connect, that leverages IAM to grant permissions to connect to it. (this is something we're currently implementing as Stacktape, and will be ready in ~2 weeks).
- Fluent shell scripts with JavaScript
-
Testing in ReScript
For FE, it’s usually Cypress or Playwright; for BE, it’s to run a server and start sending requests; for CLI, I like the tool called execa.
-
How to use execa@6 with NestJs?
Since version 6 execa is pure ES module. An attempt to import a package into NestJS project results in an error:
-
Getting vim ex command output without a TTY?
Essentially when I run this from my shell I get a listing of keymaps configured for vim. However, when I run it from a program without a PTY or TTY (e.g., via Rust's Command or Node's execa) I get an exit code of 0 and no output.
What are some alternatives?
keep-a-changelog - If you build software, keep a changelog.
zx - A tool for writing better scripts
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
Electron - :electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
git-cliff - A highly customizable Changelog Generator that follows Conventional Commit specifications ⛰️
nodegit - Native Node bindings to Git.
Release It! 🚀 - 🚀 Automate versioning and package publishing
schemapack - Create a schema object to encode/decode your JSON in to a compact byte buffer with no overhead.
release-please - generate release PRs based on the conventionalcommits.org spec
hypernova - A service for server-side rendering your JavaScript views
rn-boilerplate - React native boilerplate with formik, ui kittens, eslint setup, and expo
nan - Native Abstractions for Node.js