search

adam-26 / react-script-tag

A react <script> tag that supports universal rendering
MIT License
19 stars 6 forks source link

Errors when I clone this repository and run tests. #22

Closed Wounded-Knee closed 3 years ago

Wounded-Knee commented 3 years ago 
falken@Joshua:~/RepotDepot$ git clone git@github.com:adam-26/react-script-tag.git
Cloning into 'react-script-tag'...
remote: Enumerating objects: 407, done.
remote: Counting objects: 100% (407/407), done.
remote: Compressing objects: 100% (407/407), done.
remote: Total 1173 (delta 268), reused 0 (delta 0), pack-reused 766
Receiving objects: 100% (1173/1173), 425.15 KiB | 512.00 KiB/s, done.
Resolving deltas: 100% (908/908), done.
Checking connectivity... done.

falken@Joshua:~/RepotDepot$ cd react-script-tag/
falken@Joshua:~/RepotDepot/react-script-tag$ npm i; npm test
added 734 packages from 470 contributors and audited 739 packages in 14.038s
found 1748 vulnerabilities (756 low, 72 moderate, 917 high, 3 critical)
  run `npm audit fix` to fix them, or `npm audit` for details

> react-script-tag@1.1.2 pretest /home/falken/RepotDepot/react-script-tag
> npm run lint

> react-script-tag@1.1.2 lint /home/falken/RepotDepot/react-script-tag
> eslint ./src

Oops! Something went wrong! :(

ESLint: 4.17.0.
ESLint couldn't find the plugin "eslint-plugin-prettier". This can happen for a couple different reasons:

1. If ESLint is installed globally, then make sure eslint-plugin-prettier is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.

2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

    npm i eslint-plugin-prettier@latest --save-dev

If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! react-script-tag@1.1.2 lint: `eslint ./src`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the react-script-tag@1.1.2 lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/falken/.npm/_logs/2021-01-23T21_26_53_884Z-debug.log
npm ERR! Test failed.  See above for more details.