parcel
Skill15 starsChanged 47 days agoMITView on GitHub
Expert Parcel assistance covering zero-configuration bundling, transformer plugins, SVG/CSS/SCSS asset pipelines, code splitting, and multi-target builds. Use when bundling web apps without complex Webpack setups, configuring .parcelrc, debugging build caches, or compiling modern JavaScript.
- Deletes or force-pushes
- Installs packages
3 other projects use a version of this.
Adopted by
Most recently taken up by
- kvyb/context-parceltheir own version, first seen Aug 3, 2026
- 0xSero/parcelstheir own version, first seen Jul 14, 2026
- theYahia/pochta-russia-mcptheir own version, first seen Mar 31, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- 0xSero/parcels★ 171same name
- kvyb/context-parcel★ 2same name
- theYahia/pochta-russia-mcp★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository350 other files it gives its agents.
- airflowSkill
- catboostSkill
- claudeSkill
- comfyuiSkill
- cursor-aiSkill
- dalleSkill
- daskSkill
- dbtSkill
- deepseekSkill
- fastaiSkill
- geminiSkill
- github-copilotSkill
- huggingfaceSkill
- jaxSkill
- jupyterSkill
- kerasSkill
- langchainSkill
- lightgbmSkill
- llamaindexSkill
- llamaSkill
- matplotlibSkill
- midjourneySkill
- mistralSkill
- mlflowSkill
- nltkSkill
- numpySkill
- ollamaSkill
- openai-gptSkill
- opencvSkill
- pandasSkill
- perplexitySkill
- plotlySkill
- polarsSkill
- pytorchSkill
- raySkill
- scikit-learnSkill
- seabornSkill
- spacySkill
- sparkSkill
- stable-diffusionSkill
- tensorflowSkill
- vaexSkill
- weights-biasesSkill
- whisperSkill
- xgboostSkill
- api-gatewaySkill
- clean-architectureSkill
- cqrsSkill
- domain-driven-designSkill
- event-drivenSkill
- event-sourcingSkill
- graphqlSkill
- grpcSkill
- hexagonalSkill
- microservicesSkill
- modular-monolithSkill
- monolithSkill
- rest-apiSkill
- sagaSkill
- serverlessSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 120
Solution: Create .parcelrc extending default config.
- Very specific: line 155
Use HTML files as entrypoints (parcel src/index.html) so Parcel automatically detects all dependent scripts, styles, and assets.
- Very specific: line 163
Commit .parcel-cache or dist/ directories to version control.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Parcel
Parcel is the "Zero Config" bundler. It works out of the box for React, Vue, Rust (Wasm), and more. v2.12 uses Lightning CSS for extreme performance.
When to Use
- Zero-Config Web Application Bundling: Bundling modern web apps, TypeScript, JSX, SCSS, and HTML without manual configuration.
- High-Performance Rust-Based Compilation: Leveraging SWC-based transpilation and multithreaded caching out of the box.
- Full-Stack Asset Pipelines: Bundling SPAs, web workers, WebAssembly, and service workers automatically from HTML entrypoints.
- Micro-Frontend & Library Building: Outputting ESM, CommonJS, and UMD bundles with automated source maps.
Quick Start
1. Initialize and Run Parcel
npm install --save-dev parcel// package.json
{
"name": "my-app",
"source": "src/index.html",
"scripts": {
"start": "parcel",
"build": "parcel build"
},
"devDependencies": {
"parcel": "^2.12.0"
}
}2. Start Dev Server
npm start
# Server listening on http://localhost:1234Core Concepts
HTML-First Bundling & Zero-Config Setup
Building a TypeScript React application starting directly from index.html:
<!-- src/index.html -->
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Parcel React App</title>
<link rel="stylesheet" href="./styles.scss" />
</head>
<body>
<div id="root"></div>
<script type="module" src="./index.tsx"></script>
</body>
</html>Production Build & Library Configuration (package.json)
Configuring dual ESM and CommonJS library output with automated types:
{
"name": "my-shared-library",
"version": "1.0.0",
"source": "src/index.ts",
"main": "dist/index.cjs",
"module": "dist/index.mjs",
"types": "dist/index.d.ts",
"scripts": {
"start": "parcel src/index.html --port 3000 --open",
"build": "parcel build src/index.html --dist-dir build --public-url /",
"build:lib": "parcel build"
},
"devDependencies": {
"@parcel/packager-ts": "^2.12.0",
"@parcel/transformer-sass": "^2.12.0",
"@parcel/transformer-typescript-types": "^2.12.0",
"parcel": "^2.12.0"
}
}Advanced Pipeline Customization (.parcelrc)
Extending the default pipeline with custom transformers and compressors:
{
"extends": "@parcel/config-default",
"transformers": {
"*.svg": ["@parcel/transformer-svg", "@parcel/transformer-svgo"]
},
"compressors": {
"*.{html,css,js,svg}": [
"@parcel/compressor-gzip",
"@parcel/compressor-brotli"
]
}
}Common Patterns
Custom .parcelrc Pipeline Extension
Problem: Need custom asset transformation (e.g. SVG inlining or custom minifier) alongside default presets.
Solution: Create .parcelrc extending default config.
{
"extends": "@parcel/config-default",
"transformers": {
"*.svg": ["@parcel/transformer-svg", "..."]
},
"reporters": ["...", "@parcel/reporter-bundle-analyzer"]
}Multi-Target Library and Browser Output
Problem: Build a library for both modern browser ESM and CommonJS node usage.
Solution: Declare multiple targets in package.json.
{
"name": "lib-core",
"source": "src/index.ts",
"main": "dist/index.cjs",
"module": "dist/index.mjs",
"types": "dist/index.d.ts",
"targets": {
"main": {},
"module": {}
}
}Best Practices
Do:
- Use HTML files as entrypoints (
parcel src/index.html) so Parcel automatically detects all dependent scripts, styles, and assets. - Configure
targetsinpackage.jsonwith Browserslist queries for precise polyfill generation. - Cache
.parcel-cacheacross CI/CD pipeline runs to achieve instantaneous subsequent builds. - Enable
--detailed-reportduring production builds to analyze asset bundle weights.
Don't:
- Mix conflicting custom webpack configs inside Parcel projects; rely on
.parcelrc. - Commit
.parcel-cacheordist/directories to version control. - Manually compile Sass or TypeScript before passing files to Parcel; let Parcel handle the transformation pipeline.
Troubleshooting
| Error | Cause | Solution |
| Stale build output or cache corruption | .parcel-cache/ containing invalid serialized graph states | Run rm -rf .parcel-cache dist and restart parcel. |
@parcel/core: Failed to resolve module | Relative import missing extension or package missing in dependencies | Verify file path casing, ensure module is listed in package.json dependencies. |
Production build fail: Target "main" declared in package.json but source is an HTML file | main field mistakenly points to .js when bundling single-page HTML app | Remove "main": "index.js" from package.json when building web applications. |
References
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

