Parcel Zero-Config Bundling Quiz Quiz

Explore the core concepts and best practices of zero-configuration bundling using Parcel, including entry points, plugin handling, and project structure. This quiz is designed to help developers assess their understanding of how Parcel simplifies the build process with minimal setup.

1. Understanding Default Entry Point Resolution

   When initializing a project with Parcel and without providing any config files, which file will Parcel automatically use as the default entry point if available in the project root?

   1. entry.config.js
   2. parcel.config.json
   3. main.bundle
   4. index.html

   Explanation: Parcel looks for 'index.html' by default as the entry point if no configuration is provided, which allows it to automatically handle web projects. 'entry.config.js' and 'parcel.config.json' are not automatically recognized as entry points. 'main.bundle' refers to a potential output file, not an entry, making it incorrect. This automatic detection is part of Parcel's zero-config philosophy.

2. Interpreting Asset Type Handling

   A developer includes JavaScript, CSS, and image files in their project folder with no configuration or plugin setup; how does Parcel process these different asset types during a zero-config build?

   1. It automatically detects and bundles all recognized file types.
   2. It skips CSS files unless explicitly named bundle.css.
   3. It requires a plugin configuration for handling images.
   4. It only bundles JavaScript files and ignores others.

   Explanation: Parcel is designed to automatically recognize, process, and bundle many common asset types such as JavaScript, CSS, and images without manual configuration. The option stating only JavaScript files are bundled is wrong because it supports much more. While plugins may add additional capabilities, image handling works out of the box. CSS files are not required to be named specifically, so the fourth option is also incorrect.

3. Configuring Output Folder

   If a user runs Parcel with zero-config and does not provide an explicit output directory, where are the generated bundled files placed by default?

   1. In a directory named 'public'
   2. In a folder named 'dist'
   3. At the project root folder
   4. Inside a folder called 'builds'

   Explanation: With zero-configuration, bundled files are output to a folder named 'dist' by default, which keeps sources and output separate. 'builds' and 'public' are common alternatives in other tools but are not the defaults here. Outputting to the project root is incorrect because it would lead to a cluttered directory and is not the default behavior.

4. Plugin Discovery in Zero-Config Environments

   Without a configuration file, how does Parcel identify and apply plugins or transformers needed for various file types during a typical zero-config build?

   1. It scans for 'plugin.js' in each subdirectory.
   2. It cannot use any plugins and skips unsupported files.
   3. It prompts the user interactively to choose plugins while building.
   4. It relies on built-in auto-detection and compatible installed dependencies.

   Explanation: Parcel leverages its built-in mechanism to auto-detect both file types and any compatible plugins found in project dependencies, making configuration unnecessary for basic tasks. It does not scan for specific files like 'plugin.js', nor does it prompt users for plugin choices. The notion that it cannot use plugins is incorrect since it supports automatic detection.

5. Handling Imports and Dynamic Imports

   In a zero-config setup, how does Parcel handle static and dynamic imports found in your JavaScript code, such as 'import' and 'import()' statements?

   1. It ignores dynamic imports and only processes static ones.
   2. It requires manually updating a dependency graph file.
   3. It throws errors for both static and dynamic imports without manual configuration.
   4. It automatically bundles and splits code to enable optimized loading.

   Explanation: Parcel automatically processes both static and dynamic imports, bundling modules together and splitting code when dynamic imports are used to improve performance. Ignoring or throwing errors for imports is not accurate in a zero-config context. Manual dependency graph updates are not necessary due to Parcel’s automated approach.