Our great sponsors
grunt | rimraf | |
---|---|---|
17 | 16 | |
12,254 | 5,484 | |
0.1% | - | |
3.7 | 5.8 | |
5 months ago | about 1 month ago | |
JavaScript | TypeScript | |
GNU General Public License v3.0 or later | ISC 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.
grunt
-
How to improve page load speed and response times: A comprehensive guide
Many web pages use CSS and JavaScript files to handle various features and styles. Each file, however, requires a separate HTTP request, which can slow down page loading. Concatenation comes into play here. It involves combining multiple CSS or JavaScript files into a single file. As a result, pages load faster, reducing the time spent requesting individual files. Gulp, Grunt, and Webpack are some of the tools that can assist you in speeding up the concatenation process. They enable seamless merging of many files during development, ensuring deployment readiness.
-
Build a Vite 5 backend integration with Flask
Once you build a simple Vite backend integration, try not to complicate Vite's configuration unless you absolutely must. Vite has become one of the most popular bundlers in the frontend space, but it wasn't the first and it certainly won't be the last. In my 7 years of building for the web, I've used Grunt, Gulp, Webpack, esbuild, and Parcel. Snowpack and Rome came-and-went before I ever had a chance to try them. Bun is vying for the spot of The New Hotness in bundling, Rome has been forked into Biome, and Vercel is building a Rust-based Webpack alternative.
-
Understanding package.json II: Scripts
Keep scripts independent: Keep your scripts independent of each other to avoid dependency issues. If you need to run one script after another, use a task runner like Gulp or Grunt to define tasks and their dependencies.
-
JavaScript Module Bundlers and all that Jazz ✨
Browserify was great at bundling scripts, but what if we need to transform code - Say compile CoffeeScript to JavaScript, for this, a new group of tools for the web was born, which focussed on running code transforms. These are usually called task runners, and the most popular ones are Grunt and Gulp.
-
The Emperor's New Library
What we see, a decade ago, are that many of the "popular" libraries, frameworks, and methods, not surprisingly, have gone by the wayside, a lot that have remained in current code as difficult-to-removemodernize legacy cruft (Bower, Gulp, Grunt, Backbone, Angular 1, ...), and then we have the small minority that are still here. Some that remain have had their utility lessened/questioned by platform and language improvements (jQuery, lodash, ...), but very, very few exist that are the same now as they were then. Another fun historical reference: issue #118 of "JavaScript Weekly" (February 22, 2013) includes a first link out to asm.js.
- Which tool for bundling ts and sass in a plain old php website
-
Who still uses Grunt.js?
Grunt.js is a favorite tool of mine, while it's most commonly viewed as a (legacy) build system, I've found it to be a fairly robust CLI framework for designing local and automated tasks and still actively develop tasks to this day.
-
userscript-modules-template
User script template that acts as module and tries to simulate imports. I built this to help me develop my user scripts, after learning about Grunt, and I thought I should share.
-
Supercharge your CSS with Tailwind
With the pre-processors, you can shrink your CSS and increase reuse through variables. In almost all working cases, it will be an improvement above vanilla CSS. There are also implementations now, via PostCSS, that add vendor prefixes for you. The major drawback is, of course, that you have to compile your CSS beforehand; usually done via part of your tooling such as Grunt or Gulp.
-
How to replace webpack & babel with Vite on a legacy React Typescript project
As far as build tools go I remember how popular Grunt was when it was first released, then it was Gulp, and Babel came along to help you add new us features and get them working on older browsers.
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
What are some alternatives?
gulp - A toolkit to automate & enhance your workflow
del - Delete files and directories
parcel - The zero configuration build tool for the web. 📦🚀
fs-extra - Node.js: extra methods for the fs object like copy(), remove(), mkdirs()
Rollup - Next-generation ES module bundler
mkdirp - Recursively mkdir, like `mkdir -p`, but in node.js
webpack - A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
proper-lockfile - An inter-process and inter-machine lockfile utility that works on a local or network file system.
Broccoli - Browser compilation library – an asset pipeline for applications that run in the browser
cross-env
webpack-dashboard - A CLI dashboard for webpack dev server
chokidar - Minimal and efficient cross-platform file watching library