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

@kilcekru/ts-basics

v3.2.0

Published

Configuration for typescript and eslint

Downloads

162

Readme

@kilcekru/ts-basics

Provides basic configuration for typescript and eslint.

Setup

npm i -D @kilcekru/ts-basics

ts-basics has a peer dependency on typescript >= 4.3
npm i -D typescript@latest

tsconfig

There are four flavours available:

  • tsconfig-node-app: for node >=16; use this for nodejs apps
  • tsconfig-node-library: for node >=16; use this for libraries (enables declaration files)
  • tsconfig-react-app: for browser; use this for react apps (es2021 is used, support for older browsers not given)
  • tsconfig-react-library: for browser, use this for libraries (enables declaration files)

To use one of those flavours, just extend your tsconfig from it:
This will give you the basic configuration, but does not specify any paths.
You still have to add include, outDir,...

Example:

{
	"extends": "@kilcekru/ts-basics/tsconfig-node-app.json",
	"compilerOptions": {
		"outDir": "dist",
	},
	"include": [
		"src/**/*"
	]
}

eslint

There are three flavours available:

  • .eslintrc.js: base config, no environment set
  • .eslintrc.node.js: environment set for nodejs
  • .eslintrc.react.js: extends for react rules, environment set for browser To use it just extend your eslintrc from this file.

Example:

module.exports = {
	env: {
		node: true,
		browser: true,
		es2020: true,
	},
	parserOptions: {
		tsconfigRootDir: __dirname,
		project: ["./tsconfig.json"],
	},
	extends: [require.resolve("@kilcekru/ts-basics/.eslintrc.js")],
};

Don't forget to add a file called .eslintignore in your project root.
Specify all files that don't need linting (like node_modules and build artifacts)

Eslint and typescript
@typescript-eslint/parser is used for all typescript files.
For this to work it is necessary that all typescript file are included in a tsconfig.json file
and this tsconfig files need to be set in parserOptions.project. Eslint will throw an error, if a file is not referenced correctly.

If you have typescript files, that are not part of your build (config, tests),
you can create a tsconfig.eslint.json which just includes those files (don't forget to add this file to parserOptions.project in the .eslintrc.js).

{
	"extends": "@kilcekru/ts-basics/tsconfig-node-app.json",
	"include": ["config/**/*", "tests/**/*"]
}

Performance
Eslint gets exponential slower on bigger projects.
If you use it in a monorepo, create a separate .eslintrc.js for each package.
Linting each package will be faster and use less memory than linting everything at once.