eslint-watch | ESLint with simple watching capabilities | Code Analyzer library

While I've not had the chance to look at your GitHub repo, from what you've posted here, one solution I'll propose is to:

1. have dev-test as part of your script that will run nodemon --exec babel-node spec/run.js in your package.json configuration
2. change the test script of your package.json to babel-node spec/run.js.

This will ensure that the tests will be run only once when a change is pushed. SO, when working locally, you can use npm run dev-test to keep the test on for the entire period you are making changes locally.

Optional catch binding was introduced in ES2019.

The specified ESLint version should be used with Node version that supports it (10 or later).

I am more interested in how do you call those images in your components rather than in the package.json (it doesn't seem a dependencies issue) because inspecting the code, it seems that you've added the /static path which is not required. As it is shown in the following screenshot:

Regarding the updates coming from the comments below, we've figured out that the issue is related directly to this GitHub issue where apparently images retrieved by a markdown are blurring. What solves the issue is to pass a withWebp parameter in Gatsby's configuration, so in gatsby-config.js:

I have resolved this issue with below steps :

1. make sure you have internet connection: ping 8.8.8.8
2. make sure you have DNS resolver working: ping www.google.com
3. make sure you can access registry.npmjs.org: ping registry.npmjs.org
4. make sure you can connect via https.

Run below command in npm command prompt or Visual Studio Code terminal.

npm config rm proxy

npm config rm https-proxy

Try in your browser: https://registry.npmjs.org/

Make sure you are trying to connected to:

registry.npmjs.org

and not to:

"registry.npmjs.org registry.npmjs.org:443"

Use below command to set registry.

npm config set registry https://registry.npmjs.org/

If you are using a proxy to access the Web, then you also have to configure npm to use it. Use:

npm config set proxy http://username:password@proxyname:8080

npm config set https-proxy http://username:password@proxyname:8080

Points to remember here while setting above two values :

1. proxyname you need to check with your company network team. Enter that proxy URL in above 2 values.
2. If your password contains any special character then replace it with Encoded character. In this command you can’t provide a password with special character. Replace only special character not .(dot).

   Example: password is : Welcome@12# then it will be like Welcome%4012%23.

https://www.w3schools.com/tags/ref_urlencode.asp

Then try to run your npm install command and it should work.