Skip to content

chore(deps): update dependency vite to v8#390

Open
renovate[bot] wants to merge 2 commits intomainfrom
renovate/vite-8.x
Open

chore(deps): update dependency vite to v8#390
renovate[bot] wants to merge 2 commits intomainfrom
renovate/vite-8.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Mar 12, 2026

This PR contains the following updates:

Package Change
vite (source) 7.3.18.0.2

Breaking change: AMD format no longer supported

Vite 8 uses Rolldown instead of Rollup. Rolldown does not support the amd output format (rolldown#2528).

Migration to UMD

The extension-sdk has been updated to use umd instead of amd. UMD includes an AMD branch, so extensions loaded via RequireJS continue to work via the define() path.

Key changes in the extension-sdk:

  • format: 'amd'format: 'umd' (with name and globals for the UMD wrapper)
  • Removed chunkFileNames (UMD does not support code splitting)
  • Added completeUmdCurrentScriptPlugin to fix document.currentScript resolution for async module loaders (see below)

No code splitting with UMD

UMD bundles everything into a single file. Dynamic import() calls are automatically inlined. This means:

  • Extensions that used lazy loading (e.g. web-app-importer lazy-loads Uppy plugins) now load everything eagerly
  • This is the only way forward with UMD and Rolldown for now — code splitting requires ESM

document.currentScript polyfill

Vite's UMD URL resolution uses document.currentScript for relative asset paths (?url imports). However, document.currentScript is null when RequireJS calls the factory callback asynchronously, causing incorrect URL resolution.

The extension-sdk includes a plugin that captures document.currentScript at the top of the script while it's still valid. This fix has been upstreamed to Vite.

EMPTY_IMPORT_META warnings

Rolldown replaces import.meta with {} in UMD format. Three apps trigger this warning — all cases have been verified as harmless and are explicitly suppressed with per-app comments:

  • web-app-importer: Vite preload hints for inlined @UPPY dynamic imports (no-op)
  • web-app-json-viewer: Vite preload hint for inlined vanilla-picker import (no-op)
  • web-app-unzip: @zip.js/zip.js baseURI config (overridden by explicit workerURI)

Dependencies

Requires updated @opencloud-eu/extension-sdk with UMD support (not yet released).

Test plan

  • pnpm build --mode development builds all 11 extensions without errors
  • ?url asset imports resolve correctly at runtime with RequireJS
  • Verified with both vite 7 and vite 8
  • End-to-end testing of all extensions in OpenCloud

🤖 Generated with Claude Code

@renovate renovate bot force-pushed the renovate/vite-8.x branch 2 times, most recently from 07fe16f to 733267f Compare March 19, 2026 05:03
@renovate renovate bot force-pushed the renovate/vite-8.x branch from 733267f to 5fb9857 Compare March 23, 2026 14:06
Vite 8 uses Rolldown which replaces `import.meta` with `{}` in UMD
format. This triggers warnings in three apps:

- web-app-importer: Vite preload hints for @UPPY dynamic imports (no-op
  since UMD inlines all chunks)
- web-app-json-viewer: Vite preload hint for vanilla-picker dynamic
  import (same reason)
- web-app-unzip: @zip.js/zip.js baseURI config (overridden by explicit
  workerURI in useUnzipAction.ts)

All cases are harmless. Each app explicitly suppresses the warning with
a comment explaining why.
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Mar 23, 2026

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant