rimraf | execa | |
---|---|---|
16 | 20 | |
5,486 | 6,363 | |
- | - | |
5.8 | 9.6 | |
about 1 month ago | 3 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.
rimraf
-
The Bun Shell
And npmjs.com will block your IP if you do too many downloads in on day.
Actually is says 86m a week here: https://www.npmjs.com/package/rimraf
-
PURISTA: Build with rimraf, esbuild, Turbo & git-cliff
Huge thanks to Isaacs! Rimraf comes to the rescue, providing a reliable solution for deep, recursive removal of folders and files. At PURISTA, we rely on rimraf to maintain pristine build output directories.
-
Understanding package.json II: Scripts
Avoid platform-specific commands: Avoid using platform-specific commands in your scripts. Use cross-platform tools like Node.js or Bash to ensure that your scripts work on different platforms. For instance, if you want your npm script to remove a certain directory using the rm -rf command, this would work perfectly on a Linux or Mac machine but would error out on Windows. To avoid this, you can use a cross-platform package such as [rimraf](https://www.npmjs.com/package/rimraf).
-
Extended "run all specs" feature for Cypress 10
rimraf
-
The minimal setup to package and reuse your React components
Babel will overwrite but not delete any existing files or directories in the output directory. To be sure the lib folder doesn’t contain old files you can delete it before transpiling. To do this automatically you can install rimraf and add it to the transpile script like this:
-
4 reasons to avoid using `npm link`
Many packages on npm are designed to make changes to the file-system, such as rimraf or a code linter. In an accident, the consequences of running file-system altering code can be detrimental.
-
Help Deleting STONKING File Path (over 3000 char +) WS2016 File Server
Also, rimraf seems to be popular.
-
I Prefer Makefiles over Package.json Scripts
No, that's why there's a bunch of packages such as rimraf[0] that implements that sort of functionality in a cross-platform way that most people use in their scripts
[0]: https://www.npmjs.com/package/rimraf
-
TIFU by accidentally creating over 15 million files on my computer
Something that might work: rimraf. A small node script can churn through file deletion surprisingly fast on Windows. Used to use it to clear out npm packages directories at a greater than glacial pace.
-
Said it before, I'll say it again: Software Engineers are poets.
Um actually I use rimraf
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?
del - Delete files and directories
zx - A tool for writing better scripts
fs-extra - Node.js: extra methods for the fs object like copy(), remove(), mkdirs()
Electron - :electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
mkdirp - Recursively mkdir, like `mkdir -p`, but in node.js
nodegit - Native Node bindings to Git.
proper-lockfile - An inter-process and inter-machine lockfile utility that works on a local or network file system.
schemapack - Create a schema object to encode/decode your JSON in to a compact byte buffer with no overhead.
cross-env
hypernova - A service for server-side rendering your JavaScript views
chokidar - Minimal and efficient cross-platform file watching library
nan - Native Abstractions for Node.js