RangeError: Maximum call stack size exceeded
- Dominant language
- Python
- Stars
- 78.7k
- Forks
- 9.6k
- PR merge metrics
- No merged PRs in 30d
Description
@**Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
workstation# yarn dev
yarn run v1.22.22
$ vite
ERROR error when starting dev server: 00:16:50
RangeError: Maximum call stack size exceeded
at RegExp.exec ()
at /home/xw/Projects/screenshot-to-code/frontend/node_modules/dotenv-expand/lib/main.js:7:54
at Array.reduce ()
at _interpolate (/home/xw/Projects/screenshot-to-code/frontend/node_modules/dotenv-expand/lib/main.js:6:18)
at /home/xw/Projects/screenshot-to-code/frontend/node_modules/dotenv-expand/lib/main.js:36:15
at Array.reduce ()
at _interpolate (/home/xw/Projects/screenshot-to-code/frontend/node_modules/dotenv-expand/lib/main.js:6:18)
at /home/xw/Projects/screenshot-to-code/frontend/node_modules/dotenv-expand/lib/main.js:36:15
at Array.reduce ()
at _interpolate (/home/xw/Projects/screenshot-to-code/frontend/node_modules/dotenv-expand/lib/main.js:6:18)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
**Screenshots of backend AND frontend terminal logs**
If applicable, add screenshots to help explain your problem.
Contributor guide
No contributing guide indexed for this repository
Research direction
The error originates from dotenv-expand during Vite dev server startup. Examine the frontend/.env or environment variable files for circular references or recursive variable expansions. Check the dotenv-expand configuration in vite.config.js or package.json scripts. Running 'yarn dev' with debug logging or inspecting the node_modules/dotenv-expand/lib/main.js stack trace can pinpoint the problematic variable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs, vite
- Domain
- build-system, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100