node-gtk VS parcel

I'll say it because it kinda saddens me, but contributing to gnome is not a fun experience. Even though I would be normally super excited about such a request and would be happy to contibute to a FOSS project that I like (I did https://github.com/romgrk/web-toolkit and https://github.com/romgrk/node-gtk after all), my experience with many of the long term contributors to gnome has simply been too disheartening. You guys should think about why so many people are put off from contributing to gnome.

Look, all I'm saying is GTK needs to do better in terms of documentation, it has been needing it for years. I've worked on nodejs bindings for years and I've more than once stopped worked on it altogether simply out of frustration due to the absence of proper documentation for the whole ecosystem. Please, don't take all this as an attack, I'd be happy to help. But I think you're limiting the project by applying restrictions that chase those who could help.

https://parceljs.org/ is another.

It even supports languages like `` out of the box which is pretty cool.<p>IIRC it downloads necessarily plugins on the fly.

Parcel is another alternative that requires zero configuration and is super fast. If you want a simple React setup without any hassle, Parcel is a great choice.

From its documentation [1] it looks a lot like a parceljs replacement [2], i.e. a zero config bundler which processes and bundles the dependencies in .html pages. So great for simple websites, not for replacing an entire Vite stack.

[1] https://bun.sh/docs/bundler/fullstack

[2] https://parceljs.org

Packagers are the ones we most frequently come into contact with, such as Webpack Vite and Parcel. The latter may not be commonly used, but it is also a well-established tool.

npm packages dramatically sped up the productivity of developers by being able to leverage other developers' work. However, it had a major disadvantage: cjs was not compatible with web browsers. To solve this problem, the concept of bundlers was born. browserify was the first bundler which essentially worked by traversing an entry point and "bundling" all the require()-ed code into a single .js file compatible with web browsers. As time went on, other bundlers with additional features and differentiators were introduced. Most notably webpack, parcel, rollup, esbuild and vite (in chronological order).

The AI Framework Debate

You will need a web bundler. You can use parcel.js

To run this script, we need a web bundler like parcel js.

Official Website