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

@openzeppelin/docs-utils

v0.1.5

Published

Utilities for setting up and previewing documentation across OpenZeppelin projects.

Downloads

3,357

Readme

Utilities for setting up and previewing documentation across OpenZeppelin projects.

This is an internal tool for OpenZeppelin projects.

If you are looking to generate documentation for your Solidity project, check out solidity-docgen.

Initial setup (oz-docs init)

The oz-docs init command will create the necessary directories and files to include a repo in the docs site, and to preview it with the steps in the next section.

Previewing the site locally (oz-docs build, oz-docs watch)

Add a dev dependency on this repo.

npm install --save-dev github:OpenZeppelin/docs-utils
# or yarn add --dev github:OpenZeppelin/docs-utils

Use the oz-docs executable in the package's scripts. You need to provide the -c option with a path to the Antora component that you want to render (this is the directory that contains the antora.yml file).

You should add two commands: docs and docs:watch. The latter should use the oz-docs watch [PATTERN...] command. If some of the docs are generated by a prepare-docs command, e.g., extracting them from Solidity or JavaScript files, you should specifiy glob patterns that match the source files so that the docs are regenerated automatically.

   "scripts": {
+    "docs": "oz-docs -c docs",
+    "docs:watch": "npm run docs watch contracts",
     "prepare-docs": "solidity-docgen -i contracts -o docs"
   },

Setting up docs previews on pull requests

The above should enable local previews of the docs. It's also useful to set up docs previews on pull requests. This is done using Netlify Deploy Previews.

Create a netlify.toml file at the root of the repo with the following contents. (The command and the path may be slightly different for monorepos or repos using yarn.)

[build]
command = "npm run docs"
publish = "build/site"

Then create a Netlify site connected to the repository. Deploy Previews for the master branch are enabled by default.

You will want to disable the Netlify's checks on pull requests, since they are only useful for production sites. In the site settings on Netlify, go to "Build & Deploy", and at the bottom of the page go to "Deploy notifications". Delete the three notifications that say "rich details".