Explore key concepts for deploying Parcel-built applications to leading static hosting platforms with this focused quiz, covering build configurations, environment setup, asset handling, and deployment strategies. Ideal for those seeking to streamline web project deployments with optimized Parcel workflows.
When deploying a Parcel app, which directory should you specify as the publish directory to ensure only built static files are served?
Explanation: The 'dist' directory contains the output of the Parcel build process and should be published to serve only the optimized static files. The 'src' directory holds your source code, not build output. 'node_modules' contains dependencies and should never be served as is. 'config' likely holds configuration files, which are not meant to be public-facing. Using the wrong directory may expose unnecessary files or break your deployment.
Which build command should you set in your deployment settings for a typical Parcel project using the default configuration?
Explanation: 'parcel build' triggers Parcel to bundle and optimize your app for production deployment. 'npm install' only installs dependencies and does not build the project. 'npm run dev' starts a development server, which isn't suitable for production hosting. 'node server.js' is used for starting backend servers, not for building static assets. Setting the correct build command ensures only optimized output is generated.
To ensure a single page app built with Parcel serves index.html for all routes (for example, navigating to /about), which file should you include in the root of your published directory?
Explanation: Including an '_redirects' file allows the hosting platform to route all requests to index.html, which is essential for clean URL support in single page apps. 'robots.txt' is for search engine crawlers, not routing. '.parcelrc' is a build configuration file unrelated to routing. '.env' files store environment variables, not routing rules. The '_redirects' file ensures your app's navigation works as intended.
If your Parcel app uses environment variables for API keys or secrets, where is the safest place to set these during deployment?
Explanation: Environment variables should be set in the platform's deployment settings for security and flexibility; this keeps them out of your codebase. Placing them in 'index.html' or hardcoding in your JavaScript exposes sensitive data to the public. Documenting variables in 'README.md' is informative but does not actually set them for the build process. Secure handling of environment variables protects your app and users.
If your images and assets are not appearing after deployment of a Parcel app, which configuration issue is most likely the cause?
Explanation: An incorrect public URL setting can cause the app to generate asset paths that do not match their deployed location, leading to missing files. A syntax error in 'style.css' may affect styles but won't usually break asset loading. A version mismatch in 'package.json' can cause build issues, but not typically broken asset paths. Uncommitted changes in '.gitignore' affect version control, not deployment output. Always verify public URL settings for proper static asset delivery.