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

implicit

v0.0.2

Published

Syntax checking helper

Downloads

36

Readme

implicit

JavaScript Syntax Check Helper

Implicit checks your JavaScript code and reports on potential errors with the syntax of the code. These are errors that cannot be found with a linter.

For example, can you see the error in the following code?

if(Object.keys(o) === 1) {
  console.log(o);
}

It should be:

if(Object.keys(o).length === 1) {
  console.log(o);
}

Implicit will generate an error if it encounters a mistake such as this.

Implicit is not a replacement for a linter. It is an additional tool that you run to check your code. A good place to put this is in a pre-commit hook.

Install

npm install -g implicit

Usage

Run inside the root of your project:

implicit

Generate default rc and ignore files:

implicit init

Get usage help:

implicit --help

Development

If you've clone the repo and are working on changes you can install your local version of implicit by running this in the root of the implicit project folder:

npm i -g .

Now you can go to another project and run implicit to have your customized changes run against your project.

Contributing and Pull Requests

See Contributing.

Help

You can contact me on Twitter: @wildfiction