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

@tsrx/eslint-parser

v0.3.118

Published

ESLint parser for Ripple (.tsrx files)

Readme

@tsrx/eslint-parser

npm version npm downloads

ESLint parser for TSRX files. This parser enables ESLint to understand and lint .tsrx files by default, using the shared TSRX parser from @tsrx/core.

Installation

pnpm add --save-dev '@tsrx/eslint-parser'
# or
npm install --save-dev '@tsrx/eslint-parser'
# or
yarn add --dev '@tsrx/eslint-parser'

Usage

Flat Config (ESLint 9+)

// eslint.config.js
import tsrxParser from '@tsrx/eslint-parser';
import tsrxPlugin from '@tsrx/eslint-plugin';

export default [
  {
    files: ['**/*.tsrx'],
    languageOptions: {
      parser: tsrxParser,
    },
    plugins: {
      ripple: tsrxPlugin,
    },
    rules: {
      ...tsrxPlugin.configs.recommended.rules,
    },
  },
];

Legacy Config (.eslintrc)

{
  "overrides": [
    {
      "files": ["*.tsrx"],
      "parser": "@tsrx/eslint-parser",
      "plugins": ["ripple"],
      "extends": ["plugin:ripple/recommended"]
    }
  ]
}

How It Works

This parser uses the shared TSRX parser (@tsrx/core) to parse TSRX files into an ESTree-compatible AST that ESLint can analyze.

The parser:

  1. Parses the TSRX source code (.tsrx)
  2. Normalizes the AST for ESLint traversal
  3. Returns the ESTree AST to ESLint
  4. Allows ESLint rules to analyze TSRX-specific patterns

Supported Syntax

The parser supports TSRX syntax including:

  • Native TSRX elements and fragments as JavaScript expressions
  • JSX statement containers with @{ ... } for setup plus one rendered output
  • Template directives like @if, @for, @switch, and @try
  • Function components that return TSRX, TSX, or standard JavaScript values
  • track() reactive values (imported from ripple)
  • &{} and &[] lazy destructuring
  • Reactive collections
  • All standard JavaScript/TypeScript syntax

Example

Given a .tsrx file:

import { track } from 'ripple';

export function Counter() @{
  let &[count] = track(0);

  <button onClick={() => count++}>
    Increment
    <span>{count}</span>
  </button>
}

The parser will successfully parse this and allow ESLint rules (like those from @tsrx/eslint-plugin) to check for:

  • Track calls at module scope
  • Missing @ operators
  • Invalid rendering control flow
  • And more

Related Packages

License

MIT

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.