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

@ripple-ts/eslint-plugin

v0.3.3

Published

ESLint plugin for Ripple

Readme

@ripple-ts/eslint-plugin

npm version npm downloads

ESLint plugin for Ripple - helps enforce best practices and catch common mistakes when writing Ripple applications.

Works just like eslint-plugin-react - simply install and use the recommended config!

Installation

npm install --save-dev '@ripple-ts/eslint-plugin'
# or
yarn add --dev '@ripple-ts/eslint-plugin'
# or
pnpm add --save-dev '@ripple-ts/eslint-plugin'

Usage

Flat Config (ESLint 9+)

// eslint.config.js
import ripple from '@ripple-ts/eslint-plugin';

export default [...ripple.configs.recommended];

The plugin automatically:

  • Detects and uses @ripple-ts/eslint-parser if installed for .ripple files
  • Detects and uses @typescript-eslint/parser if installed for .ts/.tsx files
  • Excludes .d.ts files, node_modules, dist, and build directories from linting
  • Works with both .ts/.tsx and .ripple files

Legacy Config (.eslintrc)

{
  "plugins": ["ripple"],
  "extends": ["plugin:ripple/recommended"]
}

Configurations

recommended

The recommended configuration enables all rules at their default severity levels (errors and warnings).

import ripple from '@ripple-ts/eslint-plugin';

export default [
  {
    plugins: { ripple },
    rules: ripple.configs.recommended.rules,
  },
];

strict

The strict configuration enables all rules as errors.

import ripple from '@ripple-ts/eslint-plugin';

export default [
  {
    plugins: { ripple },
    rules: ripple.configs.strict.rules,
  },
];

Rules

ripple/no-module-scope-track (error)

Prevents calling track() at module scope. Tracked values must be created within a component context.

Incorrect:

// This will cause runtime errors
let globalCount = #ripple.track(0);

export component App() {
  <div>{@globalCount}</div>
}

Correct:

export component App() {
  // track() called within component
  let count = #ripple.track(0);

  <div>{@count}</div>
}

ripple/require-component-export (warning)

Warns when capitalized components are not exported. This helps ensure components are reusable across modules.

Incorrect:

component MyButton() {
  <button>Click me</button>
}
// MyButton is defined but not exported

Correct:

export component MyButton() {
  <button>Click me</button>
}

ripple/prefer-oninput (warning, fixable)

Recommends using onInput instead of onChange for form inputs. Unlike React, Ripple doesn't have synthetic events, so onInput is the correct event handler.

Incorrect:

<input onChange={handleChange} />

Correct:

<input onInput={handleInput} />

This rule is auto-fixable with --fix.

ripple/no-return-in-component (error)

Prevents returning JSX from Ripple components. In Ripple, JSX should be used as statements, not expressions.

Incorrect:

export component App() {
  return <div>Hello World</div>;
}

Correct:

export component App() {
  <div>Hello World</div>
}

ripple/unbox-tracked-values (error)

Ensures tracked values are unboxed with the @ operator when used in JSX expressions.

Incorrect:

export component App() {
  let count = #ripple.track(0);

  // Missing @ operator
  <div>{count}</div>
}

Correct:

export component App() {
  let count = #ripple.track(0);

  // Properly unboxed with @
  <div>{@count}</div>
}

ripple/no-introspect-in-modules (error)

Prevents using the @ introspection operator in TypeScript/JavaScript modules. In .ts/.js files, you should use get() and set() functions instead.

Incorrect:

// count.ts
export function useCount() {
  const count = #ripple.track(1);
  #ripple.effect(() => {
    console.log(@count); // Error: Cannot use @ in TypeScript modules
  });
  return { count };
}

Correct:

// count.ts
import { get, set } from 'ripple';

export function useCount() {
  const count = #ripple.track(1);

  // Use get() to read tracked values
  const double = #ripple.track(() => get(count) * 2);

  #ripple.effect(() => {
    console.log('count is', get(count));
  });

  return { count, double };
}

Note: The @ operator is only valid in .ripple component files. In TypeScript modules, use get() to read values and set() to update them.

Custom Configuration

You can customize individual rules in your ESLint config:

export default [
  {
    plugins: { ripple },
    rules: {
      'ripple/no-module-scope-track': 'error',
      'ripple/require-component-export': 'off', // Disable this rule
      'ripple/prefer-oninput': 'error', // Make this an error instead of warning
      'ripple/no-return-in-component': 'error',
      'ripple/unbox-tracked-values': 'error',
      'ripple/no-introspect-in-modules': 'error',
    },
  },
];

The plugin will automatically detect and use the Ripple parser for your .ripple files.

License

MIT

Contributing

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

Related