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

oxlint-plugin-raula

v0.0.1

Published

Opinionated oxlint rules and a shareable config preset for JSX/module.css Next.js app standards.

Readme

oxlint-plugin-raula

Opinionated oxlint rules and a shareable config preset for Next.js app standards. This is a port of eslint-plugin-raula's JS/TSX rules to oxlint's JS Plugin API. The JS Plugin API itself is still alpha as of writing — Vercel's AI SDK already runs a custom oxlint JS Plugin in production, so this is past the "wait and see" stage, but expect rough edges.

This package covers two raula rules that check JS/TSX source. Rules that check Tailwind class usage more thoroughly (exhaustive-tailwind-classes) and CSS files themselves (exhaustive-tailwind-theme-tokens, no-disallowed-global-class-selectors, no-document-element-styles-in-css) are not covered here — see eslint-plugin-raula and stylelint-plugin-raula.

no-await-in-layout (present in eslint-plugin-raula) is deliberately not ported here. Next.js's own Cache Components feature (cacheComponents: true in next.config.ts) already catches this — and more broadly: it flags any uncached/dynamic data access (fetch(), cookies(), headers(), params, searchParams, connection()) blocking prerendering anywhere in the render tree, not just in layouts, as a build error with three labeled fixes (stream/cache/block). Since raula and Cache Components are both opt-in, prefer enabling Cache Components over maintaining a narrower custom lint rule for the same problem.

Setup

Install the package:

npm install -D oxlint oxlint-plugin-raula
pnpm add -D oxlint oxlint-plugin-raula
yarn add -D oxlint oxlint-plugin-raula
bun add -d oxlint oxlint-plugin-raula

Extend the shareable preset in .oxlintrc.json:

{
	"extends": ["./node_modules/oxlint-plugin-raula/.oxlintrc.json"]
}

Or register the plugin and pick individual rules yourself:

{
	"jsPlugins": ["./node_modules/oxlint-plugin-raula/index.mjs"],
	"rules": {
		"raula/no-inline-style-prop": "error",
		"raula/no-css-modules": "error"
	}
}

There is no CLI installer yet (unlike the eslint/stylelint packages) — you need to add the extends entry to your .oxlintrc.json by hand.

Rules

raula/no-inline-style-prop

Disallows inline style props in JSX.

raula/no-css-modules

Disallows importing *.module.css files.

Design note: the eslint-plugin-raula version of this rule lints the *.module.css file itself by filename, via ESLint's CSS language plugin. oxlint cannot lint CSS files at all, so this version instead flags the import site in JS/TSX (import styles from "./page.module.css"). Trade-off: an unused, unimported .module.css file is no longer caught, but a real import always is.

Testing

There is no ESLint-RuleTester-equivalent for oxlint rules. Tests run the real oxlint CLI against fixture files under fixtures/ and assert on the JSON diagnostics output — see tests/output.test.ts.

pnpm test