rollup: PARSE_ERROR when code contains "process.env ="

Describe the bug

The error caused by phaser library . And then I found: if the code contains process.env=<any> and run vite build, it will raise a rollup parserError.

Reproduction

Write process.env={} any where and run vite build.

System Info

• required vite version: 1.0.0-rc.4
• required Operating System: MacOS 10.15.7
• required Node version: 14.7.0

[hyrious]

@hyrious I’d be interested on how to “apply the hack on every post install”. My machine I can open up the node_modules and remove the line, but the build machines won’t work that way. This webpack world is not something I am very knowledgeable on as far as my options.

This is quite easy, you can come up with a hack.ts: https://gist.github.com/hyrious/6817207816032d532a10e53e4c3daac8

Then in package.json:

"postinstall": "ts-node -O \"{\\\"module\\\":\\\"commonjs\\\"}\" hack.ts",

---

BTW, I’ve tried mermaid in vite2, it seems there’s no such issue at all.

[jbjorge]

It would be great if we could figure out a workaround together. It might seem like process.env = {} is a byproduct from webpack (or whichever bundler the library creators use) making builds runnable in the browser.

In my project

▶ grep -iRl "process.env = {}" ./node_modules | wc -l
17 (packages)

In the source of one of the dependencies that contain it

▶ grep -iRl "process.env = {}" ./node_modules | wc -l
35 (packages)

I suspect we would need to ask a lot of maintainers to change their builds if we want to get rid of this error without using a workaround.