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

biome-plugin-solid-router

v0.1.1

Published

Biome GritQL lint rules for @solidjs/router — catches common API mistakes at lint time

Downloads

200

Readme

biome-plugin-solid-router

Biome GritQL lint rules for @solidjs/router. Catches common API mistakes from React Router muscle memory at lint time.

Rules

| Rule | Description | |------|-------------| | solid-router-no-link-component | Flags Link import from @solidjs/router and <Link> usage with router props (to, href). Use <A> instead. | | solid-router-no-to-prop | Flags to= prop on <A> components. Use href= instead. | | solid-router-no-initial-entries | Flags initialEntries prop on <MemoryRouter>. Use createMemoryHistory() instead. | | solid-router-no-routes-wrapper | Flags Routes import or usage from @solidjs/router. Place <Route> directly inside <Router>. | | solid-router-no-element-prop | Flags element= prop on <Route>. Use component= instead. |

Install

npm install -D biome-plugin-solid-router

Setup

Add the rules you want to your biome.json or biome.jsonc:

{
  "plugins": [
    "./node_modules/biome-plugin-solid-router/rules/solid-router-no-link-component.grit",
    "./node_modules/biome-plugin-solid-router/rules/solid-router-no-to-prop.grit",
    "./node_modules/biome-plugin-solid-router/rules/solid-router-no-initial-entries.grit",
    "./node_modules/biome-plugin-solid-router/rules/solid-router-no-routes-wrapper.grit",
    "./node_modules/biome-plugin-solid-router/rules/solid-router-no-element-prop.grit"
  ]
}

Pick only the rules relevant to your project — you don't have to use all of them.

Requirements

  • Biome >= 2.0.0 (GritQL plugin support)

How it works

Each rule is a .grit file using Biome's GritQL engine (engine biome(1.0)) to match AST patterns. The rules catch common mistakes developers make when migrating from React Router to @solidjs/router:

  • Import detection: Flags imports of non-existent components (Link, Routes) from @solidjs/router.
  • Prop detection: Flags wrong prop names (to instead of href, element instead of component, initialEntries which doesn't exist).
  • Scoped matching: Import rules only match @solidjs/router imports — Link from other packages is fine. JSX <Link> is only flagged when router-specific props (to, href) are present, avoiding false positives from icon libraries like lucide-solid.

What these rules don't cover

Some @solidjs/router mistakes require type information that GritQL doesn't have access to:

  • Passing JSX instead of a component reference to component= (needs to know the value type)
  • Route params type mismatches (needs type inference)
  • Missing required route config options (needs full API schema)

For full type-aware linting, use these rules alongside eslint-plugin-solid.

License

MIT