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-remark-lint-no-liquid-directive-include

v1.0.1

Published

Lint rule that prevents remark ::include from referencing files that contain LiquidJS syntax.

Readme

remark-lint-no-liquid-directive-include

Lint rule that prevents ::include directives from referencing files that contain LiquidJS syntax.

Why

When a file with LiquidJS syntax (e.g. {% capture %}, {{ variable }}) is pulled in via ::include, remark processes it as plain markdown — the LiquidJS is never evaluated. This rule catches that mistake at lint time.

How it works

Before linting runs, the validate pipeline scans the shared/ directory and builds a Set of file paths that contain LiquidJS syntax. When the rule encounters an ::include directive, it checks whether the resolved file path is in that set and reports an error if so.

Error

Cannot use remark-include to include "../shared/partials/company.md": the file contains LiquidJS syntax, which remark can't process.

Example

<!-- triggers an error if company.md contains LiquidJS syntax -->
::include{src="../shared/partials/company.md"}

What counts as LiquidJS syntax

A file is considered a liquid file if its body (outside fenced code blocks and inline code spans) contains {% or {{.

<!-- detected as liquid -->
{% capture name %}Salesforce{% endcapture %}
{{ platform }}

<!-- NOT detected — inside fenced code block -->
```liquid
{% if x %}

Run the {% cycle %} tag.