What is this?
Parcel is a zero-configuration build tool for the web: it bundles and compiles JavaScript, CSS, HTML and other assets into optimized output without requiring a config file to get started.
Is this a single tool or a bunch of packages glued together?
Parcel is organized as a monorepo of many packages (core, transformers, reporters, resolvers, etc.) managed with Lerna, but you consume it as one CLI/dev-dependency called parcel.
How do I get it running on a project?
Install it as a dev dependency with yarn add --dev parcel or npm install -D parcel, then point it at an entry file, e.g. parcel index.html for dev mode or parcel build index.html for a production build.
Do I need a specific Node.js version?
Yes, Parcel's package.json requires Node.js >= 16.0.0 to run.
Can I try Parcel without installing anything?
Yes, the project builds a REPL (@parcel/repl) using a WebAssembly build of its native Rust code, letting you try bundling directly in the browser.
Is Parcel just JavaScript under the hood?
No, besides its JS/TypeScript packages, Parcel includes native Rust code that gets compiled to native binaries and to WebAssembly for performance-critical parts of the bundler.
Does Parcel only handle JavaScript bundles?
No, its topics and tooling cover JavaScript, CSS, HTML, ES6 and CommonJS modules, treating all of them as first-class assets it can bundle and compile.
Which topics is it in?
module-bundler, hmr, modules, commonjs, zero-configuration, assets, es6, build-tool, compiler, monorepo, wasm, css