Vercel Edge adapter: "process.env.NODE_ENV" in markdown files breaks build

[pilcrowonpaper]

What version of astro are you using?

2.5.0

Are you using an SSR adapter? If so, which one?

Vercel (Edge)

What package manager are you using?

pnpm

What operating system are you using?

Mac

What browser are you using?

N/A

Describe the Bug

Astros + Vercel Edge adapter fails to build when a markdown includes "process.env.NODE_ENV", but only if it's mid-string. It's specific to "process.env.NODE_ENV"; "process.env" or "process.env.ANY_OTHER_STRING" doesn't have any issues. No issues with the severless adapter as well.

Breaks:

// process.env.NODE_ENV
fn(process.env.NODE_ENV)
`process.env.NODE_ENV`

Doesn't break:

process.env.NODE_ENV
process.env.FOO

Link to Minimal Reproducible Example

https://github.com/pilcrowOnPaper/astro-markdown-edge

Participation

• I am willing to submit a pull request for this issue.

[bluwy]

We could probably do something like this to fix it, currently we're only handling import.meta.env.*.

astro/packages/astro/src/vite-plugin-markdown/index.ts

Line 118 in 5b6a031

const code = escapeViteEnvReferences(`

It also a Vite issue though because it only replaces things statically: vitejs/vite#9829

[mrthiti]

I'm facing this issue.