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

@dfinity/eslint-config-oisy-wallet

v0.5.0

Published

Shared ESLint configurations from the Oisy Wallet team

Readme

🌟 @dfinity/eslint-config-oisy-wallet

A shareable ESLint configuration library for Oisy Wallet projects, supporting both TypeScript and Svelte.

Internet Computer portal GitHub CI Checks Workflow Status

[!NOTE] This configuration is currently compatible with ESLint 9 and ESLint 10.

🖥️ Installation

# with npm
npm install --save-dev @dfinity/eslint-config-oisy-wallet
# with pnpm
pnpm add --save-dev @dfinity/eslint-config-oisy-wallet
# with yarn
yarn add -D @dfinity/eslint-config-oisy-wallet

✍️ Usage

For General Projects (Non-Svelte):

  1. Create an ESLint configuration file .eslintrc.js in your project root and extend the base configuration:
module.exports = {
  extends: ["@dfinity/eslint-config-oisy-wallet"],
};

For Svelte Projects:

  1. Create an .eslintrc.js file in your project root and extend the Svelte-specific configuration:
module.exports = {
  extends: ["@dfinity/eslint-config-oisy-wallet/svelte"],
};

For vitest test suites:

  1. Create an .eslintrc.js file in your project root and extend the vitest-specific configuration:
module.exports = {
  extends: ["@dfinity/eslint-config-oisy-wallet/vitest"],
};
  1. If the rules must apply ONLY to test files, they can be configured as:
module.exports = {
  overrides: [
    {
      // Specify the test files and/or folders
      files: [
        "**/*.test.{ts,js}",
        "**/*.spec.{ts,js}",
        "**/tests/**/*.{ts,js}",
      ],

      extends: ["@dfinity/eslint-config-oisy-wallet/vitest"],
    },
  ],
};

Finally, create an eslint-local-rules.cjs file at the root of your project containing the following:

module.exports = require("@dfinity/eslint-config-oisy-wallet/eslint-local-rules");

[!NOTE] This is necessary because the eslint-plugin-local-rules plugin we use for custom rules requires a file located at the root and does not offer any customizable location option.

🔧 Overriding, Enabling, or Disabling Rules

You can override, enable, or disable any of the rules provided by this configuration — including custom local rules — just like you would with any ESLint config.

In your .eslintrc.js, simply add a rules section:

module.exports = {
  extends: ["@dfinity/eslint-config-oisy-wallet/svelte"],
  rules: {
    // Disable a built-in rule
    "no-console": "off",

    // Disable a local custom rule
    "local/use-nullish-checks": "off",

    // Enable a built-in rule
    "local-rules/prefer-object-params": "warn",

    // Customize severity or options
    "@typescript-eslint/no-unused-vars": ["warn", { argsIgnorePattern: "^_" }],
  },
};

Or in eslint.config.ts, adding an object with the rules property:

import { default as svelteConfig } from "@dfinity/eslint-config-oisy-wallet/svelte";
import { default as vitestConfig } from "@dfinity/eslint-config-oisy-wallet/vitest";

export default [
  ...vitestConfig,
  ...svelteConfig,
  {
    rules: {
      // Disable a built-in rule
      "no-console": "off",
      "vitest/expect-expect": "off",

      // Disable a local custom rule
      "local/use-nullish-checks": "off",

      // Enable a built-in rule
      "local-rules/prefer-object-params": "warn",

      // Customize severity or options
      "@typescript-eslint/no-unused-vars": [
        "warn",
        { argsIgnorePattern: "^_" },
      ],
    },
  },
];

Note: To override local rules, make sure you have the eslint-local-rules.cjs file at the root as described above.

📐 Custom Rules

This configuration ships with several custom local rules:

| Rule | Description | | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | | local-rules/use-nullish-checks | Enforce the use of isNullish() / nonNullish() instead of direct truthiness checks for nullish assertions. | | local-rules/use-nullish-type-wrapper | Enforce proper usage of nullish type wrappers. | | local-rules/prefer-object-params | Prefer a single object parameter over multiple positional parameters. | | local-rules/no-svelte-store-in-api | Disallow importing Svelte stores in API modules. | | local-rules/no-relative-imports | Disallow relative imports; prefer alias paths. | | local-rules/explicit-non-void-return-type | Require explicit return types for functions that return a value. |

use-nullish-checks Options

The rule accepts an optional configuration object:

| Option | Type | Default | Description | | ------------------------- | --------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | includeBooleans | boolean | false | When true, also enforce nullish checks on variables typed as boolean (or boolean \| null \| undefined). Boolean expressions — comparisons, known boolean methods, literals, and negations — are always allowed regardless of this setting. | | allowFindUndefinedCheck | boolean | false | When true, allow direct nullish comparisons on the result of .find() calls (e.g. array.find(x => x) === undefined). Useful because .find() legitimately returns undefined when no match is found. |

Example:

// Enable the rule with boolean variable checking
"local-rules/use-nullish-checks": ["error", { includeBooleans: true }]

// Allow .find() results to be compared with undefined/null directly
"local-rules/use-nullish-checks": ["error", { allowFindUndefinedCheck: true }]

With includeBooleans: true:

const b: boolean = true;

// ❌ Error — boolean variable should use nonNullish()
if (b) {
}

// ✅ OK — boolean expression, always allowed
if (a === b) {
}

With allowFindUndefinedCheck: true:

// ✅ OK — .find() result compared with undefined is allowed
if (array.find((item) => item.id === id) === undefined) {
}

// ✅ OK — .find() result compared with null is allowed
if (array.find((item) => item.id === id) !== null) {
}

🛠️ TypeScript Support

If your project uses TypeScript, make sure you have a tsconfig.json file in your project root.

Here's an example tsconfig.json:

{
  "compilerOptions": {
    "strict": true,
    "target": "ESNext",
    "module": "ESNext",
    "moduleResolution": "node",
    "esModuleInterop": true,
    "skipLibCheck": true
  },
  "include": ["src/**/*.ts", "*.svelte"],
  "exclude": ["node_modules", "dist"]
}

🔍 Linting Your Project

To lint your project, add the following script to your package.json:

{
  "scripts": {
    "lint": "eslint --max-warnings 0 \"src/**/*\""
  }
}

Then, run the linting command:

npm run lint