eslint-security-scanner-configs
eslint-security-scanner-configs copied to clipboard
add package files for easier installation of dependencies and update readme
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:
- Install packages locally with
--save-dev
.- Install eslint globally to get the command everywhere.
- 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.
@lewisardern This is how I fixed it.
Please squash the commits.