This page is coding related.
Switch your preference toggle to "dev view" in the header to see this content
Tooling setup
Cirrus uses [npm scripts](https://docs.npmjs.com/misc/scripts) for its build system. Our [package.json](https://github.com/twbs/bootstrap/blob/v4.5.3/package.json) includes convenient methods for working with the framework, including compiling code, running tests, and more.
To use our build system and run our documentation locally, you'll need a copy of Cirrus's source files and Node. Follow these steps and you should be ready to rock:
- Download and install Node.js, which we use to manage our dependencies.
- Clone from the Azure Repo.
- Navigate to the root `/bootstrap` directory and run `npm install` to install our local dependencies listed in package.json.
- Install Ruby, install Bundler with `gem install bundler`, and finally run `bundle install`. This will install all Ruby dependencies, such as Jekyll and plugins. Windows users: Read this guide to get Jekyll up and running without problems.
When completed, you'll be able to run the various commands provided from the command line.
Using npm scripts
Our package.json includes the following commands and tasks:
| Task | Description |
|---|---|
npm run dist |
npm run dist creates the /dist/ directory with compiled files. Uses Sass, Autoprefixer, and terser. |
npm test |
Same as npm run dist plus it runs tests locally |
npm run docs |
Builds and lints CSS and JavaScript for docs. You can then run the documentation locally via npm run docs-serve. |
npm run superBuild |
Builds CSS and loads local server all at once. |
npm run superBuildJS |
Builds CSS, JS and loads local server all at once. |
Run `npm run` to see all the npm scripts.
Autoprefixer
Cirrus 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 .browserslistrc for details.
Local documentation
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:
- Run through the [tooling setup](#tooling-setup) above to install Jekyll (the site builder) and other Ruby dependencies with `bundle install`.
- From the root `/bootstrap` directory, run `npm run docs-serve` in the command line.
- Open `http://localhost:1337` in your browser, and voilà.
Learn more about using Jekyll by reading its [documentation](https://jekyllrb.com/docs/).
Troubleshooting
Should you encounter problems with installing dependencies, uninstall all previous dependency versions (global and local). Then, rerun `npm install`.
