vite

Description Currently, Vite determines the default as: (default) when a file is present However, some environments can create a directory without a . For example, Deno projects using in generate and use a directory for dependency resolution. In this situation, Vite still falls back to , even though exists and could be used for caching. Suggested solution If a directory exists in the project root, Vite could default to: even when is not present. Alternative Workaround Currently this can be solved by explicitly setting: I ran into this when switching a project from Node.js to Deno so I could directly use without having to wait for the next major Node.js version. After the switch, Vite started creating a folder in the project root instead of using , which was confusing at first. It works fine once is configured manually, but it would be nice if this behaved the same way across environments when a directory is present. Additional context _No response_ Validations [x] Follow our Code of Conduct [x] Read the Contributing Guidelines. [x] Read the docs. [x] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Replaced in the migration guide with so that it's easier to compose. Tested here: https://stackblitz.com/edit/vitejs-vite-wsaeavgl?file=vite.config.ts,package.json

Fixes #17608. When using rollupOptions.output.format of iife or umd without build.lib, esbuild helpers were added outside the wrapper function, causing global namespace pollution. Changed condition from checking config.build.lib to checking opts.format === iife or umd.