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

doc-jit

v1.5.0

Published

A documentation just in time to access the right doc when you need it the most

Downloads

6

Readme

Doc-JIT

Just In Time documentation.

Introduction

Display the right documentation when you need it. Doc-JIT is an VS Code extension developers to open the most relevant documentation when coding features.

Getting started

There are 2 ways to use just in time documentation:

The configuration file

This is the recommended way if you already have a documentation.

Doc-JIT uses cosmiconfig for configuration file support. You can either configure with:

  1. A "doc-jit" key in your package.json file.
  2. A .doc-jitrc file written in JSON or YAML.
  3. A .doc-jitrc.json, .doc-jitrc.yml, .doc-jitrc.yaml, or .doc-jitrc.json5 file.
  4. A .doc-jitrc.js, .doc-jitrc.cjs, doc-jit.config.js, or doc-jit.config.cjs file that exports an object using module.exports.
  5. A .doc-jitrc.toml file.

The configuration file will be resolved starting from the location of the file being formatted, and searching up the file tree until a config file is (or isn’t) found.

Example:

{
  "patterns": {
    "**/modules/**/api/**/*.hook.ts": "https://link-to-fetching-api-documentation.io",
    "**/shared/utils/**": [
      "https://link-to-shared-module-documentation.io",
      "https://link-to-util-documentation.io"
    ]
  }
}

ℹ️ You can link to the same documentation for different patterns and you can label the resources:

{
  "patterns": {
    "**.test.ts, **.spec.ts": {
      "label": "Vitest documentation",
      "uri": "https://vitest.dev/"
    }
  }
}

The documentation .doc-jit directory

If you want to have the documentation close to the code, you can in a doc-jit directory and following these steps:

  1. Create a .doc-jit directory next to src,
  2. write your documentation based on your architecture,
  3. use wildcards __ when folders have specific names (eg: modules/__/components/component.md works for modules/user/component/ or modules/book/component/)

Demo


References

Icon created by Hilmy Abiyyu A. - Flaticon