Got error messages after running npm install on my terminal

[OlusegunJoseph]

Describe the bug

I suspected most of the dependencies are no more supported and it is difficult to fix because it complains of more than one dependencies. Attached is the screen shot of error messages

Steps to reproduce

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior

I expected it to run and display the app on localhost

Is this responsiveness Issue

No

Screenshots

Desktop

• OS: [e.g. iOS]
• Browser: [e.g. chrome, safari]
• Version: [e.g. 22]

Smartphones

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context

No response

[saadpasta]

@OlusegunJoseph We are migrating to the nextjs and it would solve post of the issues

[frankcaoyun]

Same error here. Hope to get a fix soon.

[deathblade287]

Has it gotten fixed yet? I am facing the same error.

[BigSamu]

Same error here!

[sadapasta]

@BigSamu @AviralDhingra @frankcaoyun Please update your node version.

[BigSamu]

@saadpasta so I reinstalled NodeJS and now I am using the stable version v18.15.0 (previously using v19.6.0). After that, the installation finished succesfully but shows the following warnings:

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { npm: '^3.0.0' },
npm WARN EBADENGINE   current: { node: 'v18.15.0', npm: '9.5.0' }
npm WARN EBADENGINE }

up to date, audited 1550 packages in 2s

252 packages are looking for funding
  run `npm fund` for details

6 high severity vulnerabilities

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

However, now when I run npm start I received the following error:

> [email protected] start
> node fetch.js && react-scripts start

Fetching profile data for BigSamu
Fetching Medium blogs data for YOU MEDIUM USERNAME HERE
node:_http_client:184
      throw new ERR_UNESCAPED_CHARACTERS('Request path');
      ^

TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters
    at new NodeError (node:internal/errors:399:5)
    at new ClientRequest (node:_http_client:184:13)
    at Object.request (node:https:360:10)
    at Object.<anonymous> (/Users/samuel/Project Code/developerFolio/fetch.js:106:21)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:23:47 {
  code: 'ERR_UNESCAPED_CHARACTERS'
}

Node.js v18.15.0

Already put my Github token and username in the .env file

[BigSamu]

Ok found the problem. The project is incompatible with NodeJS v18 due to an issue with OpenSSL. I downgraded NodeJS to version 16, and the problem is fixed.

[Aladdin4u]

npm update got mine fixed

[Ashishyadav07]

Still the same error. Have you all got any fix?

[Aladdin4u]

Check for outdated dependence npm outdated then update again with npm update

[Ashishyadav07]

@Aladdin4u thank you brother.

[abdullahnasir4]

Deleting package-lock.json file solved it for me.

[aakashmanjrekar11]

@abdullahnasir4 I followed the same.

1. Cloned repo
2. Deleted package-lock.json file
3. npm install
4. npm update

After this, the package-lock.json file is recreated properly, but I still see 9 vulnerabilities.

[abdullahnasir4]

@aakashmanjrekar11 Can you try it with these steps.

1. Clone repo
2. Delete package-lock.json file
3. npm install

[aakashmanjrekar11]

@abdullahnasir4 that's what I literally said in my previous reply :) Anyways it works all right for me after those steps.

[boggodan]

@saadpasta so I reinstalled NodeJS and now I am using the stable version v18.15.0 (previously using v19.6.0). After that, the installation finished succesfully but shows the following warnings:

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { npm: '^3.0.0' },
npm WARN EBADENGINE   current: { node: 'v18.15.0', npm: '9.5.0' }
npm WARN EBADENGINE }

up to date, audited 1550 packages in 2s

252 packages are looking for funding
  run `npm fund` for details

6 high severity vulnerabilities

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

However, now when I run npm start I received the following error:

> [email protected] start
> node fetch.js && react-scripts start

Fetching profile data for BigSamu
Fetching Medium blogs data for YOU MEDIUM USERNAME HERE
node:_http_client:184
      throw new ERR_UNESCAPED_CHARACTERS('Request path');
      ^

TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters
    at new NodeError (node:internal/errors:399:5)
    at new ClientRequest (node:_http_client:184:13)
    at Object.request (node:https:360:10)
    at Object.<anonymous> (/Users/samuel/Project Code/developerFolio/fetch.js:106:21)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:23:47 {
  code: 'ERR_UNESCAPED_CHARACTERS'
}

Node.js v18.15.0

Already put my Github token and username in the .env file

I'm having the same issue. After doing the roundabout process of getting Docker to work on Windows, I finally thought it would work but I'm getting the same error just using the image/docker container, which uses node v10. I'm not a web coder and I've already spent a day trying to debug - close to giving up on this repo - I might be cursed for trying to get this work on windows though.

[Oak254]

Npm also got my error fixed

[saadpasta]

@Oak254 What was your fix? Can you create a PR for that