Rollup VS tsup

Doesn't Rollup already use quite a bit of rust[0]? It's actually why I had to abandon it for a project, where they didn't offer binaries for our build platform and I needed to bundle, like 2 ES6 javascript libraries so I just grabbed esbuild instead.

[0] https://github.com/rollup/rollup/tree/master/rust

Unlike Webpack, the Vite DevServer only compiles files when they are requested. It leverages ES module imports, which allow JS files to import other files without needing to bundle them together during development. When one file changes, only that file needs to be re-compiled, and the rest can remain unchanged. Project files are compiled with Rollup.js. Third-party dependencies in node_modules are pre-compiled using the ultra-fast esbuild bundler for maximum speed, and they are cached until the dependency version changes. Vite also provides a client script for hot module reloading.

Read the full breaking changes in Rollup’s release notes for build-related changes in build.rollupOptions.

Besides Webpack, there are many other popular web bundlers available, such as Parcel, Esbuild, Rollup, and more. They all have their own unique features and strengths, and you should make your decision based on the needs and requirements of your specific project. Please refer to their official websites for details.

The optimization points are very valid and good to keep in mind, no?

See for example:

https://github.com/rollup/rollup/issues/349

The missing minification of identifiers and properties of the Vue instance in general were always bugging me in Vue 2, even when not using the class keyword.

This is a very valid consideration IMO.

In the Node.js ecosystem, bundling is typically handled by third-party tools rather than Node.js itself. Some of the most popular bundlers in the Node.js world include Webpack, Rollup, and Parcel, offering features like code splitting, tree shaking, and hot module replacement.

📦 Rollup for bundling

Bundling: Webpack, Parcel, Rollup

Rollup is another popular JavaScript module bundler focusing on high performance. It excels at tree-shaking and uses ES module syntax to generate more performant bundles than traditional module bundlers. In addition to JavaScript, Rollup supports bundling CSS and JSON as well. Rollup has more than 12 million weekly NPM downloads.

Vite (read as vit) is actually a combination of two great frontend tools - an immensely fast development server and a build command for shipping heavily optimized static assets using Rollup. Many developers have encountered the process of setting up a project using Create React App. While CRA can be useful for beginners due to its simplicity and abstraction of configuration, it has some drawbacks that outweigh its benefits, particularly its tendency to be bloated. Don't get me wrong, Vite is opinionated as well, but it's highly extensible through its Plugin API.

Now, we can run all this server reaching the port 4000. If you want to test, build it with tsup or any other way that you want, like ts-node.

If you're building hooks, providers & components you can go with only React + TypeScript, and use something ESBuild or tsup to build it.

I am using `tsup` to transpile my application - https://github.com/egoist/tsup

I spent way to much time over the last couple days trying to line up vite/rollup to bundle my component library with types, type maps and the correct formats. Until I ran across this blog post which introduced me to https://github.com/egoist/tsup and it all just worked in a single readable command. I figured I'd share with you beautiful people so you could get your code bundled faster and carry on with the fun part of programming.

As we iterate on the definition, we are going to want a better developer experience for rebuilding the package on changes. Typically, for a “library” or “utility” style package, I’d reach for either unbuild’s stub concept or use esbuild/tsup/rollup to implement a more traditional watch/rebuild, but in this case, I’m watching a proto file that lives outsides of the source, which breaks assumptions of those tools.

My most recent project uses tsup to package a CJS and a ESM version separately, and I just publish both. It's too early to go full ESM, but I also don't want to stay on CJS, granted that we've been slowly moving away from it. To me as a dev it makes no difference, but if you want to use one or the other as a library consumer, you have a choice in my package

If you want to stay in that ecosystem, try tsup. But you should still try to wire up a canonical tsc-based project first to understand the fundamentals.

Have a look at tsup (https://tsup.egoist.dev) and microbundle (https://www.npmjs.com/package/microbundle)...

I actually recommend using tsup to build instead of tsc. It can bundle if you want, makes it easier to output multiple formats if you want, etc. It's also dead simple and lightning fast (like, MUCH faster than tasc). It's zero config so the build script is as simple as this.