🌍 Front-end Web Development · flashcards

Front-end Web Development Build Tools Flashcards

50 question-and-answer cards covering Build Tools as it is examined in Front-end Web Development. 24 of them are printed below, taken from across the deck — no signup, no paywall on the preview.

50Cards in deck
24Free preview
6Syllabus topics
~144Chars per answer
FreePrice

24 sample cards from the Build Tools deck

Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.

  1. What is the difference between Webpack's development and production modes?

    mode: 'development' optimizes for build speed and debugging (readable output, source maps); mode: 'production' enables optimizations like minification and tree shaking for smaller, faster bundles.

  2. What is tree shaking in Webpack?

    A dead-code elimination technique that removes unused exports from the final bundle. It relies on ES module static import/export syntax to detect what code is actually used.

  3. What is code splitting in Webpack?

    Breaking the bundle into multiple smaller chunks that can be loaded on demand (e.g. via dynamic import()), reducing initial load time.

  4. What is the default config file name for Webpack?

    webpack.config.js.

  5. What is Hot Module Replacement (HMR) in Webpack?

    A feature that swaps, adds, or removes modules in a running application without a full page reload, preserving application state during development.

  6. What are the four core concepts of Webpack configuration?

    Entry, Output, Loaders (module.rules), and Plugins. (Mode and devServer are also commonly configured.)

  7. What is webpack-dev-server?

    A development server that serves the bundle from memory, provides live reloading and HMR, and speeds up the develop-test loop.

  8. What is Parcel?

    Parcel is a zero-configuration web application bundler. It works out of the box without a config file, automatically handling assets, transforms, and dependencies.

  9. What is Parcel's main selling point compared to Webpack?

    Zero configuration — Parcel auto-detects and configures transforms, so developers can bundle apps without writing a config file, whereas Webpack typically requires explicit configuration.

  10. How does Parcel achieve fast build times?

    It uses multicore/parallel processing across CPU cores and a filesystem cache that persists between builds for fast incremental rebuilds.

  11. How do you typically start a Parcel project from an HTML entry?

    parcel index.html — Parcel treats the HTML file as the entry point, follows its asset references, and serves it with a dev server and hot reloading.

  12. What is Gulp?

    Gulp is a JavaScript task runner and build automation tool that uses code-over-configuration and Node.js streams to automate tasks like minification, compilation, and image optimization.

  13. What programming approach does Gulp use to define its build pipeline?

    Streaming, code-over-configuration: tasks are JS functions that pipe file streams through transformations using .pipe(), processing files in memory without temporary files.

  14. What is Gulp's configuration file named?

    gulpfile.js.

  15. What is the role of .pipe() in Gulp?

    It chains transformations together, passing the stream of files from one plugin to the next (e.g. gulp.src().pipe(sass()).pipe(gulp.dest())), avoiding intermediate files on disk.

  16. What do gulp.src() and gulp.dest() do?

    gulp.src() reads matching files into a stream (the source); gulp.dest() writes the processed stream to an output directory (the destination).

  17. What is Grunt?

    Grunt is a JavaScript task runner that automates repetitive build tasks using a configuration-over-code approach driven by a large plugin ecosystem.

  18. What is Grunt's configuration file named?

    Gruntfile.js (where tasks are configured via grunt.initConfig).

  19. What is the main architectural difference between Gulp and Grunt?

    Gulp uses code-over-configuration with in-memory streams (piping), while Grunt uses configuration-over-code where each plugin reads from and writes intermediate files to disk between steps.

  20. How does Gulp's file handling typically make it faster than Grunt?

    Gulp pipes files through transformations in memory (streams) without writing intermediate files to disk, whereas Grunt writes temporary files between each task, adding I/O overhead.

  21. What is the fundamental difference between a package manager and a module bundler?

    A package manager (npm, Yarn) installs and manages project dependencies; a module bundler (Webpack, Parcel) combines source modules and assets into optimized files for the browser.

  22. What is the difference between a task runner and a module bundler?

    A task runner (Gulp, Grunt) automates discrete build tasks (linting, compiling, copying) via a pipeline; a module bundler (Webpack, Parcel) specifically resolves a module dependency graph and outputs bundles.

  23. Classify these build tools by category: npm, Yarn, Webpack, Parcel, Gulp, Grunt.

    Package managers: npm, Yarn. Module bundlers: Webpack, Parcel. Task runners: Gulp, Grunt.

  24. What is minification, a common output of build tools?

    Removing unnecessary characters (whitespace, comments, shortening variable names) from code without changing functionality, to reduce file size and improve load performance.

What this deck covers

The Build Tools deck follows the Front-end Web Development Build Tools syllabus — 3 chapters and 6 topics — so questions land on material that is genuinely examinable rather than trivia around it. That works out to roughly 16.7 cards per chapter.

Answers are written to be recallable, not just readable — averaging about 144 characters, which is long enough to carry the reasoning and short enough to say out loud.

A deck like this earns its keep on the second and third pass. Read the syllabus first so you know the shape of the subject, then use the cards to find the specific facts that have not stuck.

Build Tools flashcards FAQ

How many Build Tools flashcards are in this Front-end Web Development deck?

50 cards. This page previews 24 of them, sampled evenly across the deck so you can judge the difficulty before installing anything.

Are these Front-end Web Development flashcards free?

Yes. The preview here is free to read with no signup, and the full 50-card deck is free inside the Examius app.

What do the Build Tools cards cover?

They follow the Front-end Web Development Build Tools syllabus — 3 chapters and 6 topics — so the questions track what is actually examinable.

How should I use these flashcards?

Read the syllabus first so you know the shape of the subject, then drill the deck. Examius schedules each card with spaced repetition, so cards you keep missing come back sooner and ones you know drift further apart.