Kickstart Bundling with Parcel: Core Features Made Easy Quiz

1. Zero configuration basics

   When you start a new project with Parcel using only an index.html that links to a script and a stylesheet, what does its zero-configuration approach mean?

   1. You can run the bundler and it will automatically detect and bundle the linked assets without adding a config file.
   2. You must create a configuration file before anything can be bundled.
   3. You need to write a custom plugin to load CSS files.
   4. Only JavaScript files are bundled, while images and CSS are ignored.
   5. A remote server must be configured before local builds can run.

2. Instant updates during development

   While developing with Parcel, you edit a CSS file and see the page update instantly without a full reload; which feature enables this behavior?

   1. Hot Module Replacement (HMR)
   2. Hard Module Reset (HMR)
   3. Hot Module Replacment (HMR)
   4. Heat Model Replacement
   5. Hot Model Reloading

3. Choosing an entry file

   In a simple setup with Parcel, which entry file type lets the bundler automatically discover linked scripts, styles, and images?

   1. An HTML file such as index.html
   2. A stylesheet like main.css
   3. A vector image like app.svg
   4. A data file such as data.json
   5. A text document like readme.md

4. Code splitting in practice

   Which approach triggers automatic code splitting in Parcel by loading a part of the app only when needed, for example when a user opens a settings panel?

   1. Using dynamic imports, for example import('./analytics-module'), will create a separate bundle that loads on demand.
   2. Using static imports, for example import './analytics-module', will always create a separate bundle.
   3. Using dynamic exports, for example export('./analytics-module'), will preload all dependencies.
   4. Using dynamic improv, for example impurt('./analytics-module'), optimizes CSS only.
   5. Using dyamic imports, for example import{'./analytics-module'}, merges all bundles into one.

5. Faster rebuilds with caching

   What is the primary benefit of Parcel’s caching during development when you make a small change to a file?

   1. It caches intermediate build results to speed up subsequent builds after small changes.
   2. It uploads your build cache to a public server for sharing.
   3. It deletes cached files on every rebuild to ensure a clean state.
   4. It disables parallel work to avoid race conditions.
   5. It caches only images and ignores code changes.