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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@salesforcedevs/sfdocs-liquid-lint-include

v1.0.6

Published

Validate '{% include "..." %}' Liquid include paths in sfdocs Markdown.

Readme

liquid-lint-include

This Markdown plugin validates {% include "..." %} paths used by the sfdocs Liquid runtime. It mirrors how liquid-runtime.ts resolves include roots so the lint reports the same set of accepted paths the SSG/runtime accepts.

What it checks

For each {% include "<path>" %} (whitespace-control variants supported), in a file with liquid.enabled: true, the rule:

  1. Rejects absolute paths and URLs (http://, https://, file://, ...).
  2. Rejects paths that escape every ancestor root (mirrors the FOLDER_LEVELS_FOR_LIQUID_ROOTS = 8 resolution in the runtime).
  3. Verifies the resolved file exists on disk.
  4. Verifies the include points to a Markdown file (.md / .markdown).
  5. Skips occurrences inside fenced and inline code (the same protection the runtime applies before parsing).

Why

@salesforcedevs/sfdocs-remark-lint-include-directive covers the :::include directive form. This rule is the Liquid analogue, for the {% include "../../shared/snippet.md" %} form added with the Liquid integration.

Install & build

yarn install && yarn build

Release versioning and commits are automated via Lerna when you merge the release PR.