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

lite-lint

v1.0.4

Published

lite-lint is a tool to ease the long time waiting for tslint/eslint in a big project.

Downloads

2

Readme

lite-lint

lite-lint is a tool to ease the long time waiting for tslint/eslint in a big project. tslint(or eslint) just lint what you configed, so if you set the whole project to lint, maybe you will wait for a long time. But infact, there is no need to lint every file, instead just lint what you modified will speed up lint progress. It's just what lite-lint does, use git status -s to collect files modified and then lint them. lite-lint only work for repository with git.

How to use

install

Use npm install -save-dev lite-lint to install or put "lite-lint": "^1.0.2", in your package.json.

configure

Just config in you package.json as bellow: for tslint:

...
"liteLint": {
	"type": "ts",
	"patterns": [
  		"src/**",
  		"sample/**"
	]
},
...

for eslint:

...
"liteLint": {
	"type": "es",
	"patterns": [
  		"src/**"
	],
	"showWarning": true
},
...

type

Whitch lint you want to use, "ts" for tslint, or "es" for eslint.

patterns

The pathes you want lite-lint to check, It's an array of pattern. lite-lint will take each path of modifed file to match every pattern, if one pattern matched, the file will be lint.

[showWarning]

A boolean value to console out warning informations of lint. false by default.

[configFile]

The path of lint config file. lite-lint will use tslint.json for tslint and use .eslintrc for eslint as default. This option is only work for tslint.

[fileTypes]

By default, lite-lint only lint .ts and .tsx files for tslint, andonly lint .js files for eslint. But you still can use fileTypes to config this behavior, it's a string separated by commas, for example "ts,tsx".