iife code generated by vite3 is not working

[Jackie1210]

Describe the bug

I was building a lib generated in iife mode, and it is not working as soon as i put it on cdn.

Reproduction

https://github.com/Jackie1210/vite-lib-iife-bug-repo

System Info

System:
    OS: macOS 11.6
    CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
    Memory: 438.13 MB / 8.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 18.6.0 - ~/.nvm/versions/node/v18.6.0/bin/node
    Yarn: 1.21.1 - /usr/local/bin/yarn
    npm: 8.13.2 - ~/.nvm/versions/node/v18.6.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Browsers:
    Chrome: 103.0.5060.134
    Firefox: 102.0
    Safari: 15.0
  npmPackages:
    vite: ^3.0.2 => 3.0.2

Used Package Manager

pnpm

Logs

No response

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 vuejs/core 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.

[bluwy]

Make sense to me. Rollup says that the name should be global, so it should be var instead.

[sapphi-red]

This seems to be an upstream issue. When generatedCode.preset = 'es2015' is set, rollup outputs the variable with const instead of var.

stackblitz

[Jackie1210]

yep，it was okay when i use vite2. I just use umd instead now.

[lukastaegert]

Interesting. While const does indeed declare variables that are defined in other script scopes, which should be good enough for IIFE, they do not end up on the global object so apparently there is a scope in between. Will need to change this. https://stackblitz.com/edit/web-platform-s6tham?devToolsHeight=33&file=script.js

[lukastaegert]

Fix at rollup/rollup#4588

[sapphi-red]

Thanks!

Closing as rollup 2.77.1 that includes the fix was released.