parcel VS webpack

Official Website

Someone even opened a discussion to ask if Parcel is dead. The official answer is no, Parcel is still alive, but it's in a we-are-working-on-a-large-refactor-and-no-time-for-minor-releases state. To us, it's like a "duck death": The latest version we can use is from more than a year ago, and we don't know when the next version will be released. It looks like it's dead, it acts like it's dead, so it's dead to us. Trust me, we tried.

While bundlers like Vite and Parcel present challenges due to our specific needs, two newer alternatives for Webpack show promise. Turbopack, the successor to Webpack created by Tobias Koppers, offers substantial performance enhancements. But, its current beta status and exclusivity for Next.js, limits its immediate usability for us.

You forgot Parcel, which is working on v3 https://parceljs.org/

We are operating within a Node environment, so our first step is to initialize our project by creating a package.json where we define dependencies and commands. Personally, I use both webpack (on top of which @wordpress/scripts is built) and Parcel. While using two different build engines may lack elegance, Parcel’s user-friendly approach compensates for this compared to webpack. Its commands are straightforward, requiring no additional configuration files. However, if you prefer using webpack exclusively, you can achieve this with just a few additions to your webpack.config.js.

Parcel is a fast and zero-configuration web application bundler designed to simplify the build process for modern web projects. It's not limited to web applications, and it can be used to build packages targeting the browser or Node.js.

At first we wanted to just get rid of all the helper utilities. Keep only the kernel, but this would mean a loss of backward compatibility. We needed some efficient code processing instead with recomposition and tree-shaking. We needed a bundler. But which one? Our testing approach relies on targets, not sources. We rebuilt the project frequently, speed was critical requirement. In essence, we chose a solution from a couple of among all available alternatives: esbuild and parcel. Esbuild won. Specifically in our case, it proved to be more productive and customizable.

It runs using Parcel, very simple and easy to setup. The app has 3 files:

Homepage: https://parceljs.org/

In the Changelog Podcast episode referenced above, Dan Abramov alluded to Parcel working on RSC support as well. I couldn’t find much to back up that claim aside from a GitHub issue discussing directives and a social media post by Devon Govett (creator of Parcel), so I can’t say for sure if Parcel is currently a viable option for developing with RSCs.

Additional Resources Google Lighthouse WebPageTest TinyPNG Webpack Documentation Service Worker API

If you're working with a modern web framework like React or Vue, you might be using something like Webpack or Rollup to bundle your assets. These tools are great, but a simpler approach to managing assets exists. This is where DAM can complement your existing build process.

Webpack is a versatile module bundler that efficiently manages assets in a web project, from JavaScript and CSS to images and fonts.

I encourage you to learn about Webpack, why it’s needed, and how you can configure it, to make the most out of Oats~i and other projects you may have using Webpack as a bundler.

Webpack is a powerful module bundler for JavaScript applications. It takes your JavaScript files and their dependencies, bundles them into a single file (or a few files), and optimizes them for the browser. Webpack has been the go-to tool for many developers for several years, thanks to its flexibility and extensive plugin ecosystem.

Official Website

Webpack is a module bundler that enables developers to bundle JavaScript files for usage in a browser.

This is particularly true for Webpack, one of the most popular bundlers in the industry, with over 30 million downloads per week.

Webpack is a bundler for JavaScript applications. It takes in multiple entry points and bundles them into optimized output files, along with their dependencies, for efficient delivery to the browser. Symfony provides a component to easily integrate webpack within your application. You can install it using composer and then npm to install the javascript required libraries:

We are operating within a Node environment, so our first step is to initialize our project by creating a package.json where we define dependencies and commands. Personally, I use both webpack (on top of which @wordpress/scripts is built) and Parcel. While using two different build engines may lack elegance, Parcel’s user-friendly approach compensates for this compared to webpack. Its commands are straightforward, requiring no additional configuration files. However, if you prefer using webpack exclusively, you can achieve this with just a few additions to your webpack.config.js.