You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-10Lines changed: 9 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,12 +14,12 @@
14
14
15
15
## Features
16
16
17
-
- 🚀 **Blazing fast** bundle times - multicore compilation, and a filesystem cache for fast rebuilds even after a restart.
18
-
- 📦 Out of the box support for JS, CSS, HTML, file assets, and more - **no plugins to install**.
19
-
- 🐠 **Automatically transforms modules** using Babel, PostCSS, and PostHTML when needed - even `node_modules`.
20
-
- ✂️ Zero configuration **code splitting** using dynamic `import()` statements.
21
-
- 🔥 Built in support for **hot module replacement**
22
-
- 🚨 Friendly error logging experience - syntax highlighted code frames help pinpoint the problem.
17
+
* 🚀 **Blazing fast** bundle times - multicore compilation, and a filesystem cache for fast rebuilds even after a restart.
18
+
* 📦 Out of the box support for JS, CSS, HTML, file assets, and more - **no plugins to install**.
19
+
* 🐠 **Automatically transforms modules** using Babel, PostCSS, and PostHTML when needed - even `node_modules`.
20
+
* ✂️ Zero configuration **code splitting** using dynamic `import()` statements.
21
+
* 🔥 Built in support for **hot module replacement**
22
+
* 🚨 Friendly error logging experience - syntax highlighted code frames help pinpoint the problem.
23
23
24
24
## Getting started
25
25
@@ -74,7 +74,7 @@ Finally, existing bundlers are built around string loaders/transforms, where the
74
74
75
75
`parcel` transforms a tree of assets to a tree of bundles. Many other bundlers are fundamentally based around JavaScript assets, with other formats tacked on - for example, by default inlined as strings into JS files. `parcel` is file-type agnostic - it will work with any type of assets the way you'd expect, with no configuration.
76
76
77
-
`parcel` takes as input a single entry asset, which could be any type: a JS file, HTML, CSS, image, etc. There are various asset types defined in `parcel` which know how to handle specific file types. The assets are parsed, their dependencies are extracted, and they are transformed to their final compiled form. This creates a tree of assets.
77
+
`parcel` takes as input a single entry asset, which could be any type: a JS file, HTML, CSS, image, etc. There are various asset types defined in `parcel` which know how to handle specific file types. The assets are parsed, their dependencies are extracted, and they are transformed to their final compiled form. This creates a tree of assets.
78
78
79
79
Once the asset tree has been constructed, the assets are placed into a bundle tree. A bundle is created for the entry asset, and child bundles are created for dynamic imports, which cause code splitting to occur. Child bundles are also created when assets of a different type are imported, for example if you imported a CSS file from JavaScript, it would be placed into a sibling bundle to the corresponding JavaScript. If an asset is required in more than one bundle, it is hoisted up to the nearest common ancestor in the bundle tree so it is not included more than once.
80
80
@@ -84,10 +84,9 @@ After the bundle tree is constructed, each bundle is written to a file by a pack
84
84
85
85
All feedback and suggestions are welcome!
86
86
87
-
- 💬 Chat: Join us on [slack](https://slack.parceljs.org/).
88
-
- 📣 Stay up to date on new features and announcements on [@parceljs](https://twitter.com/parceljs).
87
+
* 💬 Chat: Join us on [slack](https://slack.parceljs.org/).
88
+
* 📣 Stay up to date on new features and announcements on [@parceljs](https://twitter.com/parceljs).
0 commit comments