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-portsoc-ts

v0.8.9

Published

University of Portsmouth, School of Computing, ECMAScript Code Conventions

Downloads

12

Readme

eslint-config-portsoc-ts

An ESLint config for Typescript based on https://github.com/portsoc/eslint-config-portsoc.

Installation

For the stable version:

npm i --save-dev eslint eslint-config-portsoc-ts

For the latest development version:

npm i --save-dev eslint portsoc/eslint-config-portsoc-ts

Configuration

Configuration can be stored as a YAML file or added to package.json. For example, add the following in your project as .eslintrc.yml:

extends: portsoc-ts
root: true

The default environment is Node.js. To lint client-side scripts, add this to your .eslintrc.yml:

env:
  browser: true

To achieve all the above using package.json, add the following:

  "eslintConfig": {
    "extends": "portsoc-ts",
    "root": true,
    "env": {
      "browser": true
    }
  }

You will need a tsconfig.json file at the root of your project, such as this template:

  {
    "compilerOptions": {
      "outDir": "./dist-ts/",
      "sourceMap": true,
      "strictNullChecks": true,
      "strict": true,
      "noImplicitAny": true,
      "alwaysStrict": true,
      "module": "es2020",
      "target": "es2020",
      "moduleResolution": "node",
      "jsx": "react",
      "allowJs": true,
      "allowSyntheticDefaultImports": true,
      "allowUnreachableCode": false
    },
    "include": [
      "src"
    ]
  }

The include section above should point to any directories with your TypeScript and JavaScript files.

Happy linting!

Contributing

We are always delighted to receive pull requests, even for something as small as a typo.

Adding rules and tests

If you'd like to add rules that are not specific to TypeScript but also apply to JavaScript, they should be submitted to the eslint-config-portsoc package.

New TS-specific rules need to be added to the overrides section of index.js.

Tests need to be added to the /tests/files/ directory and should have a suffix depending on whether they should pass or fail linting:

  • -good.ts if the test should pass linting
  • -bad.ts if the test should fail linting
    • bad tests should always have only one instance of the error that's being checked; it's common to have one -good.ts file and multiple -bad.ts files for any rule.

Run tests with npm test.