glideapps/quicktype

'process' not defined when running quicktype-core in the browser

Open

#2031 opened on Dec 10, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (10,867 stars) (968 forks)batch import
bugdependenciesgood first issue

Description

The error before this was buffer

After running

npm install assert --save --force
npm install buffer --save --force

Now I'm getting:

Contributor guide

Tech stack
typescriptnodejs
Domain
frontenddeveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
basic webpack knowledgeunderstanding of Node globals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Investigate how to polyfill 'process' and 'buffer' in the browser environment. This typically involves configuring webpack's ProvidePlugin or using a library like 'process/browser'. Look at the quicktype core build configuration to see if it already has a browser entry or if the fix requires adding a webpack.config.js with appropriate fallbacks. Check if there are any related issues or PRs that address similar browser compatibility problems.