pkg VS parcel

You don't even need that: https://github.com/vercel/pkg.

I think there are equivalents in the Python ecosystem.

Another exciting feature is the ability to build a single-executable Node.js binary. Before Node.js v18, the only way to build a Node.js binary was to use a third-party package, like pkg.

As a comparison I am using https://github.com/vercel/pkg to package my Node.js app into an exe file. Vercel-pkg allows me to build different images for different platforms like Windows, Linux, Mac. It would be nice if it could produce a single .exe that worked on all platforms. But I guess such an exe would have to be bigger. It is not too cumbersome to produce one exe per platform that my users need.

To run NodeJS as a sidecar we need to pack it into binary. Taurine is bundling your server code and preparing it for packing into a single binary. Using Vercel’s pkg CLI tool we can compile it into a single executable binary. That binary is running with the Tauri application.

What if you packaged the whole thing into one executable using pkg?

In addition to the other responses, there are node packages like pkg and nexe that you can use to package the node executable and your code into a single executable.

Not really, at last check it just bundles the entire .Net runtime with the compiled image. It's basically the equivalent of https://github.com/vercel/pkg or similar tools.

You can even pack your terminal application in a single binary that does not require separate NodeJS installed via pkg.

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

First of all, you’ll notice that Parcel always places your bundled scripts and stylesheets in the same directory as the entry point HTML files. This happens even if you have your CSS and JavaScript files in separate folders. Since these are production files, it might not matter much. But it’s something to keep in mind. The good news is this seems to have been corrected in the upcoming Parcel version 2 (still in Alpha). So there should be a way to override this behavior when that version of Parcel is stable (the current stable version is 1.12.4).

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 landscape. Introducing Parcel.js.

After years of configuring webpack for various projects I have finally decided to migrate all my projects to Parcel[1] manly because I got tired of creating and maintaining hundreds of lines of webpack.config.js files, I wanted something that just works. I am really happy with that decision.

Parcel is plenty fast and is pretty much zero config, I can use it to build libraries[2] as well as applications[3] for the browser and node.

I am manly building client side react applications, so your mileage may vary.

[1] https://parceljs.org/

[2] https://parceljs.org/getting-started/library/

[3] https://parceljs.org/getting-started/webapp/

> I just wanna `script/build` or `yarn dev` and not think about it anymore.

Parcel might be a good fit for you: https://parceljs.org/