[BUG] using default without setting envar result in JavaScript heap out of memory

[jclaessens97]

Hello,

I've installed the package and it works perfectly in a cloud environment (where the env-var is populated). It doesn't work locally when I haven't set an .env file using the dotenv package and require the config at the first line of nuxt.config.js. If I locally just use the default option in the nuxt-env module, it results in a memory leak when trying to browse the served url.

I assume this is a bug since why else would there be an option to default the var when you have to include it with an .env file (or inline in the NPM script) anyway? 😄

If you need more info or have any more questions let me know 😉I didn't have the time to look in the code of nuxt-env to make a PR so no clue what could be the source of this problem.

[samtgarson]

Please could you provide a recreation on codesanbox? Are you sure this occurs on a fresh Nuxt app with no other code or dependencies?