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

@quintenqvd/remark-plugin-code-snippets

v1.0.1

Published

Remark plugin for sourcing code snippets from files

Downloads

28

Readme

remark-plugin-code-snippets

Remark plugin for creating sourcing code snippets from local files.

Installation

# npm
npm install remark-plugin-code-snippets

# yarn
yarn add remark-plugin-code-snippets

Options

| Option | Type | Default | Description | | :-: | :-: | :-: | :-- | | basePath | string | | base path for sourcing files. If not defined, sources files relative to the file they're referenced from. | | normalizeIndent | bool | true | normalize snippets to smallest indentation level while keeping relative indentation intact |

basePath

If specified, basePath should be relative to the project root; file paths are then sourced relative to basePath. If not specified, files paths are sourced relative to the file they're referenced from

trim

Leading and trailing lines of purely whitespace can be trimmed out based on how this option is configured.

normalizeIndent

Code snippets can have their indentation normalized in the code block while retaining relative indentation. This is particularly useful when sourcing only sections of a file.

Warning: may have unexpected behavior in the case of a mix of both tabs and spaces.

Syntax

Basic Usage

Source a file into a code block using file="path/to/file/from/basepath" in the metastring of the code block. Both single quotes and double quotes can be used, but they must match and one of them must be present.

# valid
```md file='README.md'
```

# also valid
```md file="README.md"
```

Embedding with other text

All instances of the string {{ FILE }} in the code block's contents are replaced by the file contents. This string must be on its own line, with nothing else but leading and/or trailing whitespace.

Sourcing parts of a file

Append :#-# to specify a range of lines to source from the file, rather than the entirety of the file. Leading zeros are not recognized. To source only a single line, omit the ending -#. To source from a line to the end of the file, omit the ending #.

```js file="index.js":2
```

```js file="index.js":2-3

{{ FILE:1 }}
{{ FILE }}
{{ FILE:4- }}
```

Inferring language

Use the require('remark-plugin-code-snippets).inferLanguage Remark plugin to be able to specify the file to be sourced in the node's language and infer the syntax highlighting for it based on the file extension.