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

embedex

v0.3.2

Published

Embed shared text and code snippets from source files into destination files.

Downloads

331

Readme

embedex

Embed shared text and code snippets from source files into destination files. For example:

  • Embed TypeScript examples into TypeDoc comments and your README.
  • Embed a Markdown snippet into multiple JSDoc comments.

embedex helps ensure a single source of truth while ensuring sources are up-to-date with the code they are documenting, runnable, linted, tested, and show on hover in IDEs.

Table of contents

Install

Install as a dev dependency in your project:

npm install --save-dev embedex

Or globally:

npm install --global embedex

Usage

  1. Add a source file to the ./examples directory (configurable). The first line is a comma-separated list of destination file paths to embed the source's file contents into. ./examples/greeter.ts:

    // README.md,src/greeter.ts
    import { greet } from "@my-scope/greeter";
    
    greet("world");
  2. In the destination file, add an <embedex source="..."></embedex> tag that includes the source file's path.

    • ./README.md:

      # greeter
      
      Greets a person by name.
      
      <embedex source="examples/greeter.ts">
      </embedex>
    • ./src/greeter.ts:

      /**
       * Greets a person by name.
       *
       * @example
       * <embedex source="examples/greeter.ts">
       * </embedex>
       */
      function greet(name: string) {
        console.log(`Hello, ${name}!`);
      }
  3. Run npx embedex.

  4. The source is embedded!

    • ./README.md:

      # greeter
      
      Greets a person by name.
      
      <embedex source="examples/greeter.ts">
      
      ```ts
      import { greet } from "@my-scope/greeter";
      
      greet("world");
      ```
      
      </embedex>
    • ./src/greeter.ts:

      /**
       * Greets a person by name.
       *
       * @example
       * <embedex source="examples/greeter.ts">
       *
       * ```ts
       * import { greet } from "@my-scope/greeter";
       *
       * greet("world");
       * ```
       *
       * </embedex>
       */
      function greet(name: string) {
        console.log(`Hello, ${name}!`);
      }

CLI reference

Usage: embedex [options]

Embed shared text and code snippets from source files into destination files.

Options:
  -V, --version                output the version number
  -e, --sourcesGlob <pattern>  sources glob pattern (default: "examples/**/*.{md,ts}")
  -c, --check                  verify if sources are correctly embedded without making changes,
                               exits with non-zero code if updates are needed; useful for CI/CD
                               pipelines (default: false)
  -v, --verbose                show verbose output (default: false)
  -h, --help                   display help for command

Local development commands

See package.json scripts for a list of commands.