Initializing Vite in a folder with a .env file breaks vite command

[timohermans]

Describe the bug

When I'm trying to run npm run dev on a vite project that is initialized in a folder with a .env file, breaks.

First I thought it was my Django project, but after stripping everything from the repo except the .env file, I know for certain this breaks it. The error:

error when starting dev server:
RangeError: Maximum call stack size exceeded
    at String.match (<anonymous>)
    at interpolate (path/frontend/node_modules/vite/dist/node/chunks/dep-972722fa.js:75367:28)
    at path/frontend/node_modules/vite/dist/node/chunks/dep-972722fa.js:75385:17
    at Array.reduce (<anonymous>)
    at interpolate (path/frontend/node_modules/vite/dist/node/chunks/dep-972722fa.js:75369:20)
    at path/frontend/node_modules/vite/dist/node/chunks/dep-972722fa.js:75385:17
    at Array.reduce (<anonymous>)
    at interpolate (path/frontend/node_modules/vite/dist/node/chunks/dep-972722fa.js:75369:20)
    at path/frontend/node_modules/vite/dist/node/chunks/dep-972722fa.js:75385:17
    at Array.reduce (<anonymous>)

Reproduction

https://github.com/timohermans/vite-env-bug

repro steps

git clone git@github.com:timohermans/vite-env-bug.git
cd frontend
npm install
npm run dev

System Info

System:
    OS: macOS 11.5.2
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 127.80 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.17.0 - ~/.nvm/versions/node/v14.17.0/bin/node
    Yarn: 1.22.11 - /usr/local/bin/yarn
    npm: 6.14.13 - ~/.nvm/versions/node/v14.17.0/bin/npm
  Browsers:
    Chrome: 92.0.4515.159
    Edge: 92.0.902.84
    Firefox: 90.0.2
    Safari: 14.1.2
  npmPackages:
    vite: ^2.5.1 => 2.5.1

Used Package Manager

npm

Logs

➜  frontend npm run dev -- --debug

> frontend@0.0.0 dev /Users/timohermans/projects/personal/repro/frontend
> vite "--debug"

  vite:config no config file found. +0ms
[dotenv][DEBUG] did not match key and value when parsing line 7: 
error when starting dev server:
RangeError: Maximum call stack size exceeded
    at String.match (<anonymous>)
    at interpolate (/Users/timohermans/projects/personal/repro/frontend/node_modules/vite/dist/node/chunks/dep-972722fa.js:75367:28)
    at /Users/timohermans/projects/personal/repro/frontend/node_modules/vite/dist/node/chunks/dep-972722fa.js:75385:17
    at Array.reduce (<anonymous>)
    at interpolate (/Users/timohermans/projects/personal/repro/frontend/node_modules/vite/dist/node/chunks/dep-972722fa.js:75369:20)
    at /Users/timohermans/projects/personal/repro/frontend/node_modules/vite/dist/node/chunks/dep-972722fa.js:75385:17
    at Array.reduce (<anonymous>)
    at interpolate (/Users/timohermans/projects/personal/repro/frontend/node_modules/vite/dist/node/chunks/dep-972722fa.js:75369:20)
    at /Users/timohermans/projects/personal/repro/frontend/node_modules/vite/dist/node/chunks/dep-972722fa.js:75385:17
    at Array.reduce (<anonymous>)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! frontend@0.0.0 dev: `vite "--debug"`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the frontend@0.0.0 dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/timohermans/.npm/_logs/2021-08-27T07_24_02_244Z-debug.log

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[timohermans]

Temporary fix: create an empty .env file in the frontend folder

[ghost]

Can reproduce on win10 too.

[bluwy]

This is fixed since #6995 as only .env files in the frontend project is loaded. Parent directories won't be looked for. Though from the stack trace alone, it seems to be an issue with self-referential variables on this line where dotenv-expand doesn't handle that motdotla/dotenv-expand#67. You may need to workaround this if this is used in the frontend