npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

gitbook-multi-build

v1.0.2

Published

Tool for building multiple GitBook books with single command

Downloads

7

Readme

gitbook-multi-build

Tool for building multiple GitBook books with single command. Under the hood it utilizes GitBook Toolchain to install all book plugins, build the book (as it would be build on legacy.gitbook.com) and then copy build artifact to specified directory.

Installation

npm i gitbook-multi-build

Configuration

Example configuration file (from content.gitguts.io):

{
  "books": [{
    "source": "books/introduction",
    "destination": "introduction"
  },{
    "source": "books/introduction-prework",
    "destination": "introduction-prework"
  }, {
    "source": "books/repository-prework",
    "destination": "repository-prework"
  }, {
    "source": "books/repository",
    "destination": "repository"
  }],
  "output": "dist"
}

Above JSON configuration needs to be saved in a file (f.e. books.json) and later on passed as an argument to CLI tool.

books

List of GitBook projects to build and copy over to output directory. Each book needs to have two properties:

  • source - relative path to book root directory
  • destination - name of the directory to which build book needs to be copied within specified output directory

output

Name of the directory to which all of the books will be copied after being build. Output directory will be created in directory from where tool gets executed.

Important: Output directory is considered a temporary which means that before each and every build it will be removed (if exists) and created from scratch.

Usage

Assuming configuration file is stored in file named books.json build command would look like this:

node node_modules/gitbook-multi-build/bin/index build books.json

Tool help command can be executed as following:

node node_modules/gitbook-multi-build/bin/index --help

Example tool invocation using Node.js package.json script can be found in this file.

License

MIT.

Bugs

See https://github.com/Smoczysko/gitbook-multi-build/issues.