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 🙏

© 2025 – Pkg Stats / Ryan Hefner

eslint-config-dataone

v1.0.7

Published

Package to deploy and update the DataOne Linter Files to JavaScript projects.

Readme

DataOne JavaScript Linter

This Repository is the collection of the DataOne TypeScript Linter files.

Installation

The package can be installed with the following command: npm i --save-dev eslint-config-dataone

Usage

You have to extend the ESLint File by this module. If no ESLint file is existent, create one (.eslintrc.json).

{
    "extends": [
        "eslint-config-dataone"
    ]
}

There are specific configs for the different Framework. They all inherit from the default Template:

  • default: eslint-config-dataone
  • Angular: eslint-config-dataone/angular
  • React: eslint-config-dataone/react

With the ESLint Plugin for VSCode, the errors and warnings are shown in the code directly.

To print all Errors and Warnings, you can type npx eslint . in the console. With npx eslint --fix . some Errors can be automatically fixed.

Its also possible to autofix all Problems on saving. Therefore, you have to add the following code to the VSCode Settings (Preferences > Settings > JSON view):

"editor.codeActionsOnSave": {
    "source.fixAll.eslint": true
},

Usage with Prettier

You can use ESLint in combination with the Prettier-autoformatter. To do so, following steps have to be followed.
You have to install the VSCode Extensions Prettier - Code formatter and Prettier ESLint. The Prettier ESLint Extension lets you format a File with both Prettier and ESLint.
For better usage, some configs have to adjusted. These can be found in the auxiliaryConfigs folder:

  • .vscode/settings.json
  • .editorconfig
  • prettierrc.json

Common Errors

0:0  error  Parsing error: Cannot read file 'c:\*path*\tsconfig.json'

If this Error occures, it helps to ceate a .vscode folder with a settings.json file in the root directory. In that file, you define the relative path to the project.

{
  "eslint.workingDirectories": [
    "src"
  ]
}