eslint-security-scanner-configs icon indicating copy to clipboard operation
eslint-security-scanner-configs copied to clipboard

add package files for easier installation of dependencies and update readme

Open parsiya opened this issue 5 years ago • 2 comments

Apparently there is a random error (on Windows) that is triggered when a group of modules are installed globally.

In my case, it gets triggered on some VMs. It appears that eslint and other installed packages are not detected correctly. For example,

[email protected] requires a peer of eslint@>=6.2.2 but none is installed.

We have eslint installed globally but it's not detected.

It might be related to the following known issue:

  • https://twitter.com/feross/status/1161900081492234240

The legacy-bundling workaround in the above tweet does not work here for me.

I found two solutions:

  1. Install packages locally with --save-dev.
    • Install eslint globally to get the command everywhere.
  2. Create a package. Then we can do npm install and it works.

This pull request does the second.

TODO:

  • Change some of the information inside the package.json file. I have added comments to them. For example, license and author. Probably some other stuff needed to be changed too.

parsiya avatar Dec 10 '19 18:12 parsiya

@lewisardern This is how I fixed it.

parsiya avatar Dec 10 '19 18:12 parsiya

Please squash the commits.

parsiya avatar Dec 10 '19 20:12 parsiya