Docusaurus provides a set of scripts to help you generate, serve, and deploy your website. These scripts can be invoked with the run command when using Yarn or npm. Some common commands are:
Running from the command line #
The scripts can be run using either Yarn or npm. If you've already gone through our Getting Started guide, you may already be familiar with the start command. It's the command that tells Docusaurus to run the docusaurus-start script which generates the site and starts up a server, and it's usually invoked like so:
yarn run start
The same script can be invoked using npm:
npm run start
To run a particular script, just replace the start command in the examples above with the command associated with your script.
Using arguments #
Some commands support optional arguments. For example, to start a server on port 8080, you can specify the --port argument when running start:
yarn run start --port 8080
If you run Docusaurus using npm, you can still use the command line arguments by inserting a -- between npm run <command> and the command arguments:
npm run start -- --port 8080
Configuration #
These scripts are set up under the "scripts" key in your website/package.json file as part of the installation process. If you need help setting them up again, please refer to the Installation guide.
Docusaurus provides some default mappings to allow you to run commands following Node conventions. Instead of typing docusaurus-start every time, you can type yarn run start or npm start to achieve the same.
Commands #
Reference #
docusaurus-build #
Alias: build.
Generates the static website, applying translations if necessary. Useful for building the website prior to deployment.
See also docusaurus-start.
docusaurus-examples [feature] #
Alias: examples
When no feature is specified, sets up a minimally configured example website in your project. This command is covered in depth in the Site Preparation guide. Specify a feature translations or versions to generate the extra example files for that feature.
docusaurus-publish #
Alias: publish-gh-pages
Builds, then deploys the static website to GitHub Pages. This command is meant to be run during the deployment step in Circle CI, and therefore expects a few environment variables to be defined:
GIT_USER: The git user to be associated with the deploy commit.CIRCLE_BRANCH: The git branch associated with the commit that triggered the CI run.CIRCLE_PROJECT_USERNAME: The GitHub username or organization name that hosts the git repo, e.g. "FacebookExperimental".CIRCLE_PROJECT_REPONAME: The name of the git repo, e.g. "Docusaurus".CI_PULL_REQUEST: Expected to be truthy if the current CI run was triggered by a commit in a pull request.
You can learn more about configuring automatic deployments with CircleCI in the Publishing guide.
docusaurus-rename-version <currentVersion> <newVersion> #
Alias: rename-version
Renames an existing version of the docs to a new version name.
See the Versioning guide to learn more.
docusaurus-start [--port <number>] #
Alias: start.
This script will build the static website, apply translations if necessary, and then start a local server. The website will be served from port 3000 by default.
docusaurus-version <version> #
Alias: version
Generates a new version of the docs. This will result in a new copy of your site being generated and stored in its own versioned folder. Useful for capturing snapshots of API docs that map to specific versions of your software. Accepts any string as a version number.
See the Versioning guide to learn more.
docusaurus-write-translations #
Alias: write-translations
Writes the English for any strings that need to be translated into an website/i18n/en.json file. The script will go through every file in website/pages/en and through the siteConfig.js file and other config files to fetch English strings that will then be translated on Crowdin. See the Translation guide to learn more.
