Webpack
rollup.js
Babel
Parcel
Vite
esbuild
React
npm
RequireJS
rollup.js
JSHint
stealjs
JSPM
npm
Ender
GNU Make
Webpack RequireJSRequireJS is recommended for projects that are already using it, especially if the project is large and refactoring to a different module system would be resource-intensive. It can also be suitable for legacy web applications that have complex dependency chains which have been built with AMD (Asynchronous Module Definition) patterns. However, newer projects are better served with modern bundlers and native ES6 module syntax.
Based on our record, Webpack seems to be a lot more popular than RequireJS. While we know about 253 links to Webpack, we've tracked only 14 mentions of RequireJS. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
In 2012, Webpack was released as an open-source JavaScript module bundler. It takes dependencies as input and builds a dependency graph, enabling developers to take a modular approach to web application development. This allowed them to import almost anything to client-side code and, over time, became the foundation of the build process for React, Angular, Vue, and many other frameworks. - Source: dev.to / 25 days ago
From a developer experience perspective, it's worth noting that Next.js was built using webpack for bundling, which has struggled to maintain performance. Therefore, when changing something in the code, reload times can be very slow. For this reason, the Next.js team has been working on getting full compatibility on its own bundler, Turbopack. As of Next.js 14, Turbopack is still considered beta but is much faster... - Source: dev.to / 3 months ago
The reality is simple: minification was never security. It's a size optimization that bundlers like esbuild, Webpack, and Rollup do by default. Variable renaming slows down human readers but LLMs read minified code like you read formatted code. - Source: dev.to / 4 months ago
There are also no-framework approaches. These rely directly on React-provided packages and low-level integrations with bundlers like Webpack or experimental support in tools like Bun. While technically possible, these setups are fragile. React explicitly does not guarantee stability of these internal APIs. Any team choosing this route must accept ongoing maintenance risk. - Source: dev.to / 6 months ago
Before addressing the solution, it's useful to contextualize the role of the bundler. In a modern frontend architecture, the bundler (such as webpack, rollup, or vite) has the task of traversing the application's dependency graph, resolving each import statement, to combine modules and assets into static files optimized for browser execution. - Source: dev.to / 8 months ago
That's the job of Closure Compiler. Closure is an optimizing JavaScript compiler that ClojureScript is using since its initial release, in 2011. At the time JavaScript didn't have standard module format, remember AMD, UMD, RequireJS and CommonJS? Closure folks at Google invented another one, where goog.provide declares a module and goog.require imports another module. - Source: dev.to / 9 months ago
The fact that everything was loaded synchronously, which was not really an issue at that time when writing for servers, it was not really feasible for front-ends. Therefore RequireJS was brought to live. If you ever wondered how it looks, there is an example repository still living. If you are more interested in the history, look up: AMD, UMD, RequireJS. - Source: dev.to / about 1 year ago
There is a library called requirejs (https://requirejs.org/) that accomplishes what I am referring to. However, this is essentially similar to the situation in PHP prior to version 5.3 - a solution implemented at the level of a separate library rather than at the language level. Source: about 3 years ago
Webpack is the most popular bundler and it followed on the heels of Require.js, Rollup, and similar solutions. But the learning curve for a tool like webpack is steep. Getting started with webpack isnโt easy due to its complex configurations. As a result, in recent years another solution has emerged. This tool is not necessarily a front-runner, but an easier-to-digest alternative on the front-end module bundler... - Source: dev.to / over 3 years ago
I have a number of JavaScript "classes" each implemented in its own JavaScript file. For development those files are loaded individually, and for production they are concatenated, but in both cases I have to manually define a loading order, making sure that B comes after A if B uses A. I am planning to use RequireJS as an implementation of CommonJS Modules/AsynchronousDefinition to solve this problem for me... Source: over 4 years ago
rollup.js - Rollup is a module bundler for JavaScript which compiles small pieces of code into a larger piece such as application.
Babel - Babel is a compiler for writing next generation JavaScript.
JSHint - New JSHint website. Anton Kovalyov Oct 1st, 2013. For the last couple of weeks I've been working on a new homepage for JSHint and today I'm proud to announce the new jshint. com! JSHint Website.
Parcel - Blazing fast, zero configuration web application bundler
stealjs - Futuristic JavaScript dependency loader and builder. Speeds up application load times. Works with ES6, CommonJS, AMD, CSS, LESS and more. Simplifies modular workflows.
Vite - Next Generation Frontend Tooling