Rollup VS parcel

Other popular build tools include Vite.js, Browserify, Rollup - The bundler behind vite.

Awhile back I wrote about packaging your JavaScript library code into a dual-module bundle (ESM + CommonJS) using Rollup module bundler. Make sure to check it out (it's been updated for Rollup v3!).

While searching for a solution, I came across this issue. Ironically, one of the suggested solutions in there was the initial solution described earlier above. However, there was also another suggestion.

In this blog, we'll cover how to implement a simple login signup functionality using firebase. We'll be using modular JavaScript SDK, which (according to the documentation) provides a reduced SDK size and greater efficiency with modern JavaScript build tools such as Webpack or Rollup.

My go-to front end these days is Lit with web components, rollup, and web dev server.

With tools like webpack (used by create-react-app under the hood), your entire application needs to be bundled in a single file before it can be served to the browser. Vite, on the other hand, takes advantage of native ES modules in the browser to make bundling more efficient with Rollup, serving parts of the source code as needed.

We use Vite as a dev server. This allows you to take advantage of hot reloading in development and easily build and minify code with Rollup integration. Vitest is also provided, so you can write tests in the matching folder.

In this project I use my favorite bundling tool called vite, It is a fast compiler & bundler, and it uses rollup under the hood.

While not too long, css`@apply is a lot to repeat for every class you want to “compile”. That’s why using Vite and some Rollup plugins (Vite uses Rollup under the hood) I was able to shorten it into this:

Most front-end frameworks nowadays include these features as part of their CLI’s such as Create React App, Angular’s ng-cli, etc. For those that don’t, many will use a combination of some type of bundler like Parcel, Rollup, or Webpack and a browser refresher like livereload. This enables you to write code, save it, and immediately see the results. This in turn leads to fast feedback as you iterate all day in this build loop. The native Elm Reactor doesn’t offer this ability and elm-live fits the bill as a small Node.js library to enable this.

Parcel is a popular zero configuration build tool for the web. Some of its popular features include -

Parcel is a JavaScript bundler for Web applications with zero configuration and is straight-forward to set up. It packages all the application files in a dist folder, so the application can be run.

Sounds like you're looking for ParcelJS https://parceljs.org/

parcel-bundler cache (https://parceljs.org/)

FWIW, I'm using https://pnpm.io and https://parceljs.org to handle collecting and building the static assets for .js (Alpine and HTMX) and .css (Tailwind). I found it cleaner separation of concerns to let the JavaScript tooling manage the JavaScript dependencies, and have been happy with the performance and flexibility of this approach.

It's a React application written in TypeScript using Parcel.

- Data export.

Feel free to leave feedback here or on GitHub[3]. Perhaps it could be helpful to you as well. Cheers!

1. https://parceljs.org/

A bundler lets you write modular code and bundle it together into small packages to optimize load time. Popular bundlers: webpack, Parcel, esbuild, swc.

Most front-end frameworks nowadays include these features as part of their CLI’s such as Create React App, Angular’s ng-cli, etc. For those that don’t, many will use a combination of some type of bundler like Parcel, Rollup, or Webpack and a browser refresher like livereload. This enables you to write code, save it, and immediately see the results. This in turn leads to fast feedback as you iterate all day in this build loop. The native Elm Reactor doesn’t offer this ability and elm-live fits the bill as a small Node.js library to enable this.

Parcel