APOD request fails with uncaught "process is not defined"

Open Beginner friendly
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript, react, webpack
Domain
frontend

Research direction

Reproduce the failure by clicking the “Fetch APOD” button in /my-react-app/nasa-api, then start with src/utilities/apiUrl.js and its buildApiUrl entry point. Check the webpack 5 setup in relation to the process.env reference; done means the APOD request completes without an uncaught “process is not defined” error.

Written by the indexing model from the issue text.

Description

Clicking on the "Fetch APOD" button in "/my-react-app/nasa-api" results in an uncaught exception:

ReferenceError: process is not defined
    at buildApiUrl (webpack://my-react-app/./src/utilities/apiUrl.js?:6:16)
    ...

A little searching on the topic suggests that this may be due to webpack 5 dropping some automatic
polyfills that were included automatically in previous versions, including the polyfill that provided process.env.

Dominant language
JavaScript
Stars
4
Forks
2
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.