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

check-es-version

v1.5.0

Published

A tool used to check the ECMAScript compatibility of JavaScript packages.

Downloads

43

Readme

check-es-version

A tool used to check the ECMAScript compatibility of a JavaScript package and all its dependencies recursively.

Installation

yarn add --dev check-es-version

Usage

check-es-version --es-version=<esVersion> \
  --package-name=<packageName> \
  --require-resolve-path=<requireResolvePath> \
  --show-dependency-tree=<showDependencyTree> \
  --show-error=<showError> \
  --check-peer-dependency=<checkPeerDependency> \
  [--target-file=<targetFile>] \
  [--target-dir=<targetDir>]

where

  • --es-version=<esVersion> or -e <esVersion>: The ECMAScript compatibility version to check. Default value is 5.
  • --package-name=<packageName> or -p <packageName>: The name of the package to check. Default value is ., indicating the package in the current directory.
  • --require-resolve-path=<requireResolvePath> or -r <requireResolvePath>: The path where to resolve the dependent packages. Default value is ., indicating the program will try to resolve the path of the dependent packages in the ./node_modules directory.
  • --show-dependency-tree=<showDependencyTree> or -t <showDependencyTree>: Whether to display the dependency tree. Default value is false. If the project has a very deep dependency tree, display the dependency tree may cause an unreadable output.
  • --show-error=<showError> or -s <showError>: Whether to display the detailed parsing errors of each incompatible packages. Default value is false.
  • --check-peer-dependency=<checkPeerDependency> or -c <checkPeerDependency>: Whether to check the peerDependencies of the packages. Default value is false.
  • --target-file=<targetFile> or -f <targetFile>: If this argument is specified, the program will only check the compatibility of the specified file.
  • --target-dir=<targetDir> or -d <targetDir>: If this argument is specified, the program will check the compatibility of the all JavaScript files in the specified directory.
  • --help or -h: Show the command line help messages.

Examples

First execute the following command to install the package:

yarn add --dev check-es-version

Then add the following command in the package.json:

"scripts": {
  ...
  "es5": "./node_modules/.bin/check-es-version -e 5 -p .",
  ...
}

Now you can use yarn es5 to check the ES5 compatibility of your library and all its dependencies.

If you project is not a library, for example, a Quasar App. You can add the following command to your package.json:

"scripts": {
  ...
  "es5": "./node_modules/.bin/check-es-version -e 5 -d ./dist/spa/js/",
  "es5:dep": "./node_modules/.bin/check-es-version -e 5 -p .",
  ...
}

The first command yarn es5 will check the compatibility of all compilied JavaScript files of your App. If you find some JS file is incompatible, you can execute the second command yarn es5:dep to check the compatibility of all dependencies of your App. If you find some dependency is incompatible to ES5, you can add it to the build.transpileDependencies option of quasar.conf.js.