Inject environment variables

Use case: I have NEXT_PUBLIC_DEPLOYMENT_URL. In order to read it I have to use manually dotenv, which is not ideal.

[reubn]

While I’d agree that injecting environment variables wouldn’t be in scope for a standalone sitemap generator, I don’t agree that it shouldn’t be in scope for this project: given its tight coupling with Next.js.

Next.js injects environment variables. If this was a normal Next.js plugin (i.e. one that made use of webpack / the next.config.js file) then the variables would be injected. It’s only due to the mechanism behind this plugin that they aren’t - but to ensure a consistent DX, surely it would be preferable that they are.

It’s a 2 line fix with no dependencies other than Next.js itself:

const env = require('@next/env')

env.loadEnvConfig(process.cwd(), process.env.NODE_ENV === 'development')

[iamvishnusankar]

@reubn I totally missed this since you commented on a closed issue. I have added support for .env loading. Consider mentioning my username or reopen the issue next time.

@ilgarm It’s here.