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

ilinter-test

v1.0.1

Published

iLinter is useful for linting your code with ESLint rules and guidelines.

Downloads

2

Readme

iLinter

This project is useful for linting your code with ESLint rules and guidelines.

Installation (local)

For installing ESLint locally in your project you need to run below commands:

Installation (Global)

For installing globally you need to run below commands:

NPX

You can run npx command as well as mentioned below:

Project Linting (On Command Line or terminal)

For linting the project one need to run above script which has been added inside scripts object of your projects package.json file.
User can edit the script as per requirements.

Project Linting (Generating Report - By Default HTML Format)

For generating report one need to run the above script which has been added inside scripts object of your projects package.json.
User can change the format by replacing --format html option by mentioned values [checkstyle,codeframe,compact,html,jslint-xml,json-with-metadata,json,junit,stylish,table,tap,unix,visualstudio] in the script.

Fixing linting errors

For fixing linting errors one just need to run above command. We have added a script inside scripts tag in your projects package.json

Removing package

Description

After basic package installation user will be prompted if s/he is using Typescript.
For input as y or Y, an npm package named eslint-config-uxp-ts-linter will be installed.
For input as n or N, an npm package named eslint-config-uxp-es-linter will be installed.
Pressing any other key will abort the process and user will have to run the command again.
Changes will be done in various files namely:

  1. package.json: This package will install dependency related to linting for Typescript. It will also include few scripts in "scripts" object of package.json
  2. A file called .eslintrc.js will be generated which will be extending the linting package, also user can write his/er specific rules in this file under the rules object. User rules will be given preference over the installed package.
  3. A backup file will be generated for package.json and any file including name like .eslintrc so that if the user wants to use his/er earlier package s/he can directly use the code from the backup file.

Note

ESLint version required >=6.x.x