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

polyjuice

v2.2.4

Published

A utility to converts JSHint and JSCS files into ESLint and vice-versa

Downloads

488

Readme

Build Status Coverage Status Code Climate npm version

Converts .jshintrc and .jscsrc files into .eslintrc and vice-versa

Polyjuice is a utility that converts JSHint and JSCS files into ESLint files and the other way around.

Install

$ npm install --save-dev polyjuice

Usage

var polyjuice = require('polyjuice')

var to_eslint = {
  jshint: polyjuice.from.jshint(['./.jshintrc']),
  jscs  : polyjuice.from.jscs(['./.jscsrc']),
  both  : polyjuice.to.eslint(['./.jshintrc'], ['./.jscsrc'])
}

var to_jscs_and_jshint = {
  jshint: polyjuice.to.jshint(['./.eslintrc')],
  jscs  : polyjuice.to.jscs(['./.eslintrc')],
  both  : polyjuice.from.eslint(['./.eslintrc'])
}

When using polyjuice.from.eslint an object with keys jscs and jshint is returned.

CLI

If installed globally, you can use polyjuice as a command line utility. You can check which rules have been discarded by adding --discarded or -d to your command.

To ESLint

You must provide the files to be assessed by using the options --jshint and --jscs, for instance:

$ polyjuice --jshint .jshintrc --jscs .jscsrc > .eslintrc

Note you are allowed to pass in any number of files

To JSHint and JSCS

You must provide the file to be assessed by using the option --eslint and also which output you want by using either --to-jshint or --to-jscs, for instance:

$ polyjuice --eslint .eslintrc --to-jshint > .jshintrc

Note you are allowed to pass in any number of files

Contributing

Contributions are always welcome! If you want to have a better understanding about the conversion files, I encourage you to take a look at the conversion page. You can also check the rules discarded when parsing JSCS, parsing JSHint and parsing ESLint.

Versions used

These are the versions used as source of the translation. Therefore, you may expect all rules up to those versions to have been mapped to the target tool.

  • ESLint: v1.7.2
  • JSCS: v3.0.2
  • JSHint: v2.9.2

License

MIT