Learn how to use Bootstrap’s included npm scripts to build our documentation, compile source code, run tests, and more.
To use our build system and run our documentation locally, you’ll need a copy of Bootstrap’s source files and Node. Follow these steps and you should be ready to rock:
/bootstrapdirectory and run
npm installto install our local dependencies listed in package.json.
gem install bundler, and finally run
bundle install. This will install all Ruby dependencies, such as Jekyll and plugins.
When completed, you’ll be able to run the various commands provided from the command line.
Our package.json includes the following commands and tasks:
| ||Same as |
npm run to see all the npm scripts.
Bootstrap uses Autoprefixer (included in our build process) to automatically add vendor prefixes to some CSS properties at build time. Doing so saves us time and code by allowing us to write key parts of our CSS a single time while eliminating the need for vendor mixins like those found in v3.
We maintain the list of browsers supported through Autoprefixer in a separate file within our GitHub repository. See /package.json for details.
Running our documentation locally requires the use of Jekyll, a decently flexible static site generator that provides us: basic includes, Markdown-based files, templates, and more. Here’s how to get it started:
npm run docs-servein the command line.
http://localhost:9001in your browser, and voilà.
Learn more about using Jekyll by reading its documentation.
Should you encounter problems with installing dependencies, uninstall all previous dependency versions (global and local). Then, rerun
© 2011–2018 Twitter, Inc.
© 2011–2018 The Bootstrap Authors
Code licensed under the MIT License.
Documentation licensed under the Creative Commons Attribution License v3.0.