evanw/node-source-map-support

'Uncaught ReferenceError: process is not defined' in Chrome

Open

#262 opened on Nov 21, 2019

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (2,078 stars) (242 forks)batch import
bughelp wanted

Description

I do get an 'Uncaught ReferenceError: process is not defined' error in Chrome since version 0.5.15. It seems to be caused by issue #255, commit a64d497 line 362 in source-map-support.js Chrome Version 78.0.3904.97 (Official Build) (64-bit) node 10.5.0/10.17.0 Problem did not occur for me in FireFox, Edge, Safari. Only in Chrome.

Contributor guide

Tech stack
javascriptnodejs
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
familiarity with Node.js process globalknowledge of browser environment
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
The bug is introduced in commit a64d497 at line 362 of source map support.js, where `process` is used without a guard. The error occurs in Chrome because `process` is not defined. To fix, add a check for `typeof process !== 'undefined'` before accessing `process.env`. Alternatively, consider bundling with a webpack define plugin to replace `process` references. Check the issue comments for any context about the intended behavior. Then create a pull request that conditionally uses `process` only when available.