TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters

[unknowwww]

Describe the bug

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

Fetching profile data for YOUR GITHUB USERNAME HERE
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 ClientRequest (node:_http_client:184:13)
at Object.request (node:https:379:10)
at Object. (/Users/yw/Downloads/untitled folder/developerFolio/fetch.js:106:21)
at Module._compile (node:internal/modules/cjs/loader:1546:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1691:10)
at Module.load (node:internal/modules/cjs/loader:1317:32)
at Module._load (node:internal/modules/cjs/loader:1127:12)
at TracingChannel.traceSync (node:diagnostics_channel:315:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:166:5) {
code: 'ERR_UNESCAPED_CHARACTERS'
}

Node.js v22.7.0

Steps to reproduce

1. Go to 'developerFolio'
2. run npm install
3. run npm start
4. See error

Expected behavior

I'm not sure if I missed some steps. I just git clone and followed the instructions on readme. Should I edit some something or use the old version npm to let this run?

Is this responsiveness Issue

no

Screenshots

No response

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

[maisafraiz]

You should go to the file .env and change the vars "REACT_APP_GITHUB_TOKEN", "GITHUB_USERNAME" and "MEDIUM_USERNAME" before being able to do run npm start. The error is because the vars are set as "YOUR GITHUB USERNAME HERE", etc, and that is not a valid path.

The tutorial on how to change the variables are in "Linking Portfolio to GitHub".

So the order to avoid this error is:

1. Run the "How to Use" section until npm install;
2. Skip to the "Linking Portfolio to Github" section;
3. Then do npm start