Skip to content
Experimenting with git and monorepo for JavaScript Projects.
JavaScript Makefile
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
Makefile 🔥 loom Jan 21, 2020
lefthook.yml 🆕lefthook: does not run eslint on ts files Dec 21, 2019
package-lock.json 🔥 loom Jan 21, 2020
tsconfig.json 🎨 move up markdowntation makefile and readme Dec 25, 2019

My Monorepo Experiment with Git and JavaScript

Just my personal choices:



  • git
  • Node.js (tested on 12)
  • ncc
  • GNU make or BSD make
  • TypeScript (tested on 3.7) and ESLint
  • Prettier and lefthook
  • vscode or any other IDEs/editors supporting ESLint and TypeScript with JSDoc commented types


git clone
cd js
make install-deps # install dependencies
make # packaging with ncc


Serve your documentation with zero-configuration and without client side JavaScript. Inspired by GitHub Pages and docsify.


Inspired by GitHub Pages and docsify.

  • Simple (97 CLOC) and lightweight (1380kB compiled as a single file).
  • No statically built html files.
  • No JavaScript at client side.
  • Zero configuration.


Download the index.js file at GitHub releases page, and put it under your documentation directory with markdown files. Now just run node index.js and you can access your documentation site at

Matching Routes

Suppose you run node index.js under docs directory, then:

docs/        =>
docs/         =>
docs/zh-cn/  =>
docs/zh-cn/   =>
You can’t perform that action at this time.