3 ms·
I personally don't think it's that hard to run `parcel` on the command-line. Front-end tooling is as complicated as any other tooling: as much as you need it to
by Kaze404 6y ago
I personally don't think it's that hard to run `parcel` on the command-line. Front-end tooling is as complicated as any other tooling: as much as you need it to be.
- Nullabillity 6y agoParcel is easy to use (as long as you stay on the golden path), but I have a hard time calling it simple. Automagically installing dependencies that it fails to `require()` seems way out of scope for a bundler. Or managing Rust toolchains. Or a bunch of hard-coded rules that hard-exclude compiling stuff in `node_modules`. Unless they're in symlinks (presumably for Yarn workspaces?). And so on.
- markdown 6y agoThere's a new one called parcel? WTF? I started with Grunt. Then came Gulp, webpack, and a couple of others. They all do pretty much the same thing, and yet apparently someone has come up with a new one called parcel. Do they do this shit to make nice CV's so they can land FAANG jobs? Everything was easier back when we used to use FTP to upload CSS and JS files to sit alongside index.html or index.php. EDIT: I just googled and the first result is parceljs.org, but that one is blank with a BLM logo on it. Is there another site?
- deltron3030 6y agoParcel is old news, Snowpack and Vite is where it's at right now (not joking). Or you ditch node.js completely and go with Deno!
- irrational 6y agoCrap. I totally thought you were joking. The insanity must stop.
- Kaze404 6y agoAll of those you used previously still work and are arguably more used than Parcel. I only mentioned it because it's entire premise is that those bundlers are too complicated, and Parcel literally just works out of the box, no configuration, for most things. It's neat, and you might enjoy it :)