This npm package serves as a command line script designed to analyze your JavaScript, Vue, or TypeScript source code. Leveraging jsdoc-to-markdown and vue-docgen-cli, it dynamically generates markdown files tailored for VuePress.
This npm package is compatible with VuePress 2; however, it requires a version lower than 5.0.0
for proper functionality with VuePress 1.
yarn global add vuepress-jsdoc
npm i vuepress-jsdoc -g
Example:
# search code in src and move it to code (./documentation/code) in your vuepress folder (./documentation)
vuepress-jsdoc --source ./src --dist ./documentation --folder code --title API --exclude="**/*/*.test.js"
You can also use npx vuepress-jsdoc
, if you want.
If you do not want to runvuepress-jsdoc
again and again and again.
You can simply pass --watch
or -w
.
Use these options after vuepress-jsdoc
.
Name | Alias | Default | Description |
---|---|---|---|
--source | -s | ./src | Source folder with .js or .ts files |
--dist | -d | ./documentation | Destination folder |
--folder | -f | ./code | Folder inside destination folder. Gets overwritten everytime |
--title | -t | API | Title of your documentation |
--help | -h | Show help | |
--version | -v | Show current version | |
--readme | -r | Path to custom readme file | |
--exclude | -e | Pattern to exclude files/folders (Comma seperated) - *.test.js,exclude.js more information | |
--include | -e | Pattern to include files/folders (Comma seperated) - *.test.js,include.js more information | |
--rmPattern | -rm | Pattern when removing files. You can ex- and include files. (glob pattern) | |
--partials | -p | jsdoc2markdown partial templates (overwrites default ones) | |
--jsDocConfigPath | -c | Path to JsDoc Config (experimental) | |
--watch | -w | Watch changes and update markdown files |
Inside your generated folder, you can find a config.js
.
This file includes a complete filetree and an vuepress sidebar tree.
Vuepress is a static site generator by Evan You. You can add all generated documentation files to your existing vuepress project or create a new one.
# First install vuepress
yarn global add vuepress
# Run the CLI
vuepress-jsdoc
# Run vuepress dev server
vuepress dev ./documentation
# Run vuepress build, if you want to ship it
vuepress build ./documentation
Access it via: http://localhost:8080/code/
Now you need the sidebar.
Create a .vuepress
folder inside the documentation
folder and add the following config.js
.
config.js:
// auto generated sidebar
const { sidebarTree } = require('../code/config');
module.exports = {
dest: 'dist',
locales: {
'/': {
title: 'vuepress-jsdoc',
description: 'Generate jsdoc markdown files for vuepress'
}
},
themeConfig: {
editLinks: true,
sidebarDepth: 4,
docsDir: 'code',
locales: {
'/': {
nav: [
{
text: 'Home',
link: '/'
}
],
// Add the generated sidebar
sidebar: Object.assign({}, sidebarTree('Mainpage title'))
}
}
}
};
To include a custom path for your readme, simply utilize the --readme ./path/to/file.md
parameter. If you relocate a README.md
file into your source folder, the system will automatically resolve it.
For setting the title, provide it as an argument to the sidebarTree('Mainpage title')
function within your ./.vuepress/config.js
file.
Enhance your page customization by incorporating custom metadata through the @vuepress
block:
/*
* @vuepress
* ---
* title: Your custom title
* headline: You custom headline
* ---
*/
Use headline
to add a custom h1
title.
To integrate TypeScript support, install the following dev-dependencies with the following command:
npm install -D typescript jsdoc-babel @babel/cli @babel/core @babel/preset-env @babel/preset-typescript jsdoc-to-markdown
After installation, include a jsdoc.json
file in your project with specific settings, and reference it using the -c
parameter. For a comprehensive example with all the necessary configurations, refer to the ./example
folder. The example also demonstrates the usage of Babel plugins.
The ./example
folder includes a full working vuepress-jsdoc example.
# Install dependencies
npm install
# Run the CLI
vuepress-jsdoc
# Generate docs
npm run docs
# Run dev server
npm run dev
# Generate dist folder
npm run build
PRs are always welcome (: