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

@aligent/ts-code-standards

v1.4.0

Published

Standard code quality tooling for projects written in TypeScript.

Downloads

445

Readme

TS Coding Standards

Standard code quality tooling for projects written in TypeScript.

Usage

Install this package:

  # NPM
  npm install -D @aligent/ts-code-standards
  # Yarn
  yarn add -D @aligent/ts-code-standards
  # PNPM
  pnpm add -D @aligent/ts-code-standards

Copy the .editorconfig from this package into your own project:

  # Assuming your package is installed in `node_modules` folder
  cp node_modules/@aligent/ts-code-standards/.editorconfig ./.editorconfig

Add the following to your prettier.config.js:

  • For ES modules project:

    import { prettierConfig } from '@aligent/ts-code-standards';
    
    export default prettierConfig;
  • For CommonJS project:

    const { prettierConfig } = require('@aligent/ts-code-standards');
    
    module.exports = prettierConfig;

Install the ESLint and TypeScript configs:

General Projects

Add the following to your eslint.config.js:
  • For ES modules project:

    import { eslintConfigs } from '@aligent/ts-code-standards';
    
    export default [...eslintConfigs.base];
  • For CommonJS project:

    const { eslintConfigs } = require('@aligent/ts-code-standards');
    
    module.exports = [...eslintConfigs.base];
Add the following to your tsconfig.json:
{ "extends": "@aligent/ts-code-standards/tsconfigs-base" }

React Projects

Add the following to your eslint.config.js:
  • For ES modules project:

    import { eslintConfigs } from '@aligent/ts-code-standards';
    
    export default [...eslintConfigs.react];
  • For CommonJS project:

    const { eslintConfigs } = require('@aligent/ts-code-standards');
    
    module.exports = [...eslintConfigs.react];
Add the following to your tsconfig.json:
{ "extends": "@aligent/ts-code-standards/tsconfigs-react" }

Notes

  • You'll need to add include, exclude, paths etc. to your tsconfig file. These settings will be project specific.
  • Your project is considered as ES modules project if the type option in the nearest package.json is set to module. Otherwise, it's a CommonJS project. For more information on this, please check CommonJS vs. ES modules in Node.js.
  • For backward compatibility, we also export ./tsconfigs/base.json and ./tsconfigs/react.json. However, you should update to the new syntax when configuring your tsconfig.json when possible.