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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@fal-works/eslint-config-p5js

v1.0.3

Published

ESLint config for p5.js global mode. Supports TypeScript as well.

Downloads

11

Readme

@fal-works/eslint-config-p5js

ESLint config for p5.js. Supports TypeScript as well.

This config is intended for p5.js global mode.
On instance mode, just adding p5 as a global variable should be enough.

Install

npm install --save-dev @fal-works/eslint-config-p5js
yarn add --dev @fal-works/eslint-config-p5js
pnpm add --save-dev @fal-works/eslint-config-p5js

Usage

Basic config

Add the config name @fal-works/p5js to the extends list in your eslintrc.

This will add some globals and also overwrite the no-unused-vars rule.
So this should come after other extensions which also include no-unused-vars.

{
  "extends": [
    "eslint:recommended",
    "@fal-works/p5js"
  ]
}

With p5.sound

If you use p5.sound, add the config name @fal-works/p5js/sound as well.

This will add globals that are specific to p5.sound.

{
  "extends": [
    "eslint:recommended",
    "@fal-works/p5js",
    "@fal-works/p5js/sound",
  ]
}

With TypeScript

If you use TypeScript (and the @typescript-eslint plugin), use the config name @fal-works/p5js/@typescript-eslint instead.

This will:

  • turn off the default no-unused-vars rule (just like @typescript-eslint does).
  • overwrite the @typescript-eslint/no-unused-vars rule for p5.js.

So this should come after other extensions which also include @typescript-eslint/no-unused-vars.

{
  "extends": [
    "eslint:recommended",
    "plugin:@typescript-eslint/recommended",
    "@fal-works/p5js/@typescript-eslint",
  ]
}

This config does not add globals, nor does it need to; they should be managed by @types/p5, the type declaration for p5.js.
However, the type declaration may not be always up to date; sometimes you might have to escape some variables (that are not properly declared) with any, or provide additional type declaration yourself.

If using TypeScript, you can easily do a workaround instead of using this config. You can avoid no-unused-vars errors by simply exposing some functions to the global scope, like:

Object.assign(window, { setup, draw });

...so that they are not left unused. And you'll have to do this anyway if you use a module bundler.

Other

Similar libraries: