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

eslint-config-tsdocstandard

v17.1.2

Published

eslint sharable config for tsdocstandard

Downloads

61

Readme

eslint-config-tsdocstandard

eslint sharable config for tsdocstandard

Status [Experimental]

This repository contains the rules. For the tsdocstandard command go look at tsdocstandard

Rules Motivation

These rules were written to help convert vanilla JS to fully typed .js + @jsdoc with TypeScript.

You will get a LOT of lint failures about missing type annotations. That's the whole point.

If the linter passes you probably have 100% type-coverage which is awesome.

I recommend using // @ts-check & // @ts-nocheck for partial migration from JS => "typed JS + jsdoc".

Comparison with eslint-config-standard-with-typescript

There is another eslint config that includes typescript

However, that config is meant for linting *.ts typescript files using standard and eslint. This set of config is specifically for linting *.js files that use tsc --checkJs and @jsdoc comments.

The rules for typescript & javascript files are quite divergent and it's hard to have meaningful overlap.

Feedback

If you have bikeshedding suggestions about the rules please open an issue or PR.

Install

npm install -D eslint-config-tsdocstandard
# note that eslint-plugin-promise, eslint-plugin-standard, eslint-plugin-node, eslint-plugin-import & eslint-config-standard are required peer dependencies

Usage

Read up on how to use sharable configs at the eslint website.

For more details see eslint-config-standard

Contributing

Contributions welcome! Please read the contributing guidelines first.

License

ISC