Build tools configuration in Bootsrap - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the Bootstrap version in the package.json file.

Bootsrap

{
  "dependencies": {
    "bootstrap": "[1]"
  }
}

Drag options to blanks, or click blank then click option'

A"3.4.1"

B"4.6.0"

C"5.3.0"

D"6.0.0"

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing an outdated Bootstrap version like 3.x or 4.x.

Using a non-existent version number.

The correct Bootstrap version to use is 5.3.0, which is the latest stable release.

2fill in blank

medium

Complete the code to import Bootstrap's SCSS file in your main stylesheet.

Bootsrap

@import '[1]';

Drag options to blanks, or click blank then click option'

Abootstrap/dist/css/bootstrap.css

Bbootstrap/scss/bootstrap

Cbootstrap/dist/js/bootstrap.js

Dbootstrap/scss/custom

Attempts:

3 left

💡 Hint

Common Mistakes

Importing the CSS file instead of SCSS.

Importing JavaScript files by mistake.

To customize Bootstrap styles, you import the SCSS source file located at 'bootstrap/scss/bootstrap'.

3fill in blank

hard

Fix the error in the npm script to build Bootstrap SCSS using sass.

Bootsrap

"build-css": "sass [1] styles.css"

Drag options to blanks, or click blank then click option'

Ascss/styles.scss

Bsrc/styles.scss

Cbootstrap.scss

Dstyles.scss

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong file path or name that does not exist.

Confusing source and output file names.

The main SCSS file is usually named 'styles.scss' in the project root or source folder.

4fill in blank

hard

Fill both blanks to configure PostCSS plugins for autoprefixing and minification.

Bootsrap

module.exports = {
  plugins: [
    require('[1]'),
    require('[2]')
  ]
};

Drag options to blanks, or click blank then click option'

Aautoprefixer

Bcssnano

Cpostcss-import

Dtailwindcss

Attempts:

3 left

💡 Hint

Common Mistakes

Using unrelated plugins like tailwindcss or postcss-import here.

Mixing up the order of plugins.

Autoprefixer adds vendor prefixes, and cssnano minifies CSS for production.

5fill in blank

hard

Fill all three blanks to create a Webpack rule for processing SCSS files.

Bootsrap

module.exports = {
  module: {
    rules: [
      {
        test: /\.scss$/,
        use: [
          '[1]',
          '[2]',
          '[3]'
        ]
      }
    ]
  }
};

Drag options to blanks, or click blank then click option'

Astyle-loader

Bcss-loader

Csass-loader

Dfile-loader

Attempts:

3 left

💡 Hint

Common Mistakes

Including 'file-loader' which is for files, not styles.

Wrong order of loaders causing build errors.

Webpack uses 'style-loader' to inject styles, 'css-loader' to interpret CSS, and 'sass-loader' to compile SCSS.

Practice

1. What is the main purpose of build tools in Bootstrap development?

easy

A. To compile, prefix, and minify Bootstrap files for better performance

B. To write HTML code manually

C. To create images for the website

D. To host the website on the internet

Solution

1. Step 1: Understand what build tools do

   Build tools process Bootstrap files by compiling Sass, adding vendor prefixes, and minifying code.

2. Step 2: Identify the main goal

   This process makes the website faster and easier to maintain by optimizing the code.

3. Final Answer:

   To compile, prefix, and minify Bootstrap files for better performance -> Option A

4. Quick Check:

   Build tools optimize Bootstrap files = A [OK]

Hint: Build tools optimize code for speed and maintenance [OK]

Common Mistakes:

• Thinking build tools write HTML
• Confusing build tools with hosting services
• Assuming build tools create images

2. Which file extension is commonly used for Bootstrap styles before compilation?

easy

A. .css

B. .scss

C. .js

D. .html

Solution

1. Step 1: Identify Bootstrap style source files

   Bootstrap uses Sass files for styles, which have the extension .scss before compilation.

2. Step 2: Differentiate from other file types

   .css files are compiled styles, .js is JavaScript, and .html is markup.

3. Final Answer:

   .scss -> Option B

4. Quick Check:

   Sass source files = .scss [OK]

Hint: Sass files use .scss extension before compiling [OK]

Common Mistakes:

• Choosing .css which is after compilation
• Confusing JavaScript (.js) with styles
• Selecting .html which is for markup

3. Given this build tool configuration snippet for Bootstrap's JavaScript:

module.exports = {
  entry: './src/index.js',
  output: {
    filename: 'bundle.js',
    path: __dirname + '/dist'
  },
  mode: 'production'
};

What will be the result after running this build?

medium

A. An unminified JavaScript file named index.js in the src folder

B. An error because output path is incorrect

C. A CSS file named bundle.css in the dist folder

D. A minified JavaScript file named bundle.js in the dist folder

Solution

1. Step 1: Analyze the entry and output settings

   The entry point is './src/index.js', and output is set to 'bundle.js' inside the 'dist' folder.

2. Step 2: Understand the mode 'production'

   Production mode triggers minification and optimization of the JavaScript file.

3. Final Answer:

   A minified JavaScript file named bundle.js in the dist folder -> Option D

4. Quick Check:

   Production mode creates minified bundle.js in dist [OK]

Hint: Production mode bundles and minifies JS to output file [OK]

Common Mistakes:

• Thinking output file is unminified
• Confusing CSS output with JS
• Assuming error due to path syntax

4. You have this Sass build error: "Undefined variable $primary-color". What is the most likely cause in your Bootstrap build tool setup?

medium

A. You used JavaScript syntax in Sass files

B. You wrote $primary-color instead of $primary_color

C. You forgot to import Bootstrap's variables file before using $primary-color

D. Your output path is missing in the build config

Solution

1. Step 1: Understand the error message

   The error says $primary-color is undefined, meaning Sass does not know this variable.

2. Step 2: Check Sass imports

   Bootstrap variables must be imported before usage; missing import causes undefined variable errors.

3. Final Answer:

   You forgot to import Bootstrap's variables file before using $primary-color -> Option C

4. Quick Check:

   Missing variables import causes undefined variable error [OK]

Hint: Always import variables before using them in Sass [OK]

Common Mistakes:

• Assuming typo in variable name
• Blaming JavaScript syntax errors
• Thinking output path affects Sass variables

5. You want to customize Bootstrap's primary color and generate a minified CSS file using build tools. Which steps should you follow?

hard

A. Create a custom Sass file that imports Bootstrap, override $primary variable, then run Sass compiler with minification

B. Edit Bootstrap's compiled CSS file directly and rename it to .min.css

C. Change $primary variable in Bootstrap's source Sass files and run JavaScript bundler

D. Write CSS overrides in a separate file and include it without using build tools

Solution

1. Step 1: Customize Bootstrap using Sass

   Create your own Sass file that imports Bootstrap's source and override the $primary variable before import.

2. Step 2: Compile and minify with build tools

   Run the Sass compiler with minification enabled to generate optimized CSS reflecting your color change.

3. Final Answer:

   Create a custom Sass file that imports Bootstrap, override $primary variable, then run Sass compiler with minification -> Option A

4. Quick Check:

   Customize variables in Sass, then compile and minify [OK]

Hint: Override variables in Sass, then compile with minification [OK]

Common Mistakes:

• Editing compiled CSS directly instead of Sass
• Changing source Bootstrap files directly
• Skipping build tools for minification