-
Notifications
You must be signed in to change notification settings - Fork 294
Troubleshooting
Official article on the matter—Could not find a JavaScript runtime. (ExecJS::RuntimeUnavailable).
Suggested solution: Install execjs
and therubyracer
gems.
Commands to run:
gem install execjs
gem install therubyracer
Note that
therubyracer
gem may alert an issue about an installation failure. Disregard it and try building the Jekyll site again.
Issue: $ jekyll build
throws an error that it cannot locate valid web.config
in the target output directory.
Cause: This error typically occurs when you are running $ jekyll build
without specifying --destination
or if you are running the command for the first time and the output directory does not exist.
Workaround: Run $ jekyll build --destination <Target Output Directory>
. If the operation fails again, copy web.config
from the root of the documentation repository to the target output directory and run $ jekyll build
again.
- Home
- Getting Started
- Deploying Documentation on IIS
- Git and GitHub Workflow
- Handling Redirects (link to the docs-seed wiki)
- Markdown Syntax (link to the docs-seed wiki)
- Markdown Nesting (link to the docs-seed wiki)
- Using Templates (link to the docs-seed wiki)
- Using Git and Git Bash
- Faster Jekyll Build via generate_exclude.rb Script
- Using Helper Tools
- Troubleshooting
- Use VS Diff tool with Git and SourceTree