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

@brisk-docs/website

v0.9.0

Published

The Brisk website documenter

Downloads

51

Readme

Brisk Docs website generator

Brisk Docs is a package oriented documentation system that lets you write useful, interactive docs alongside your code. It is aimed at documenting packages in a mono-repo

Getting started

Start by installing Brisk Docs in your project

npm install @brisk-docs/website

To start your docs website locally:

npm run brisk dev

To produce a static build of the website that can be statically hosted:

npm run brisk build && npm run brisk export

Organising your documentation

Brisk Docs by default uses file and folder name conventions to find docs in your codebase and display them in a organised way.

Project level documentation

For guides and docs relating to your project or repository as a whole, Brisk Docs will display any Markdown or MDX files placed in the /docs folder at the top of your repository. This is a good place to put user guides, tutorials, contributor guidelines etc.

Package level documentation

Brisk Docs has first class support for multi-package repos. All packages found in the /packages directory of your project will have documentation generated automatically.

Read more about package documentation in our package documentation guide.

Using MDX

MDX means that we parse markdown a little differently, and treat jsx blocks as react components.

This means that you can write:

# Just a regular markdown package

import MyComponent from './src/myComponent'

<MyComponent>I could not be expressed just with markdown<.MyComponent>

Just some more _regular_ markdown here.

In addition to being able to render any markdown, brisk provides two components that can be used on any page without being imported.

They are <Props /> and <FileViewer /> - these are exports of pretty-proptypes and file-viewer