You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
It reproduces with and without enableGlobalCache: true on my machine.
I think this is a regression. Although the error itself is correct. remote-component.config.js resolves to nothing.
Describe the bug
I am upgrading from vite4.2 to vite4.3-beta and I expect my project can still successfully launch the dev server.
However with new vite 4.3 it cannot pass the findModuleError during dependency resolution back into the 3rd party library code https://github.com/Paciolan/remote-component/blob/master/src/getDependencies.ts#L44 for error handling.
I would consider this a regression in vite 4.3
Reproduction
https://stackblitz.com/edit/vitejs-vite-j4bqyg?file=src%2FApp.tsx,package.json&terminal=dev
Steps to reproduce
$ yarn set version berry
enableGlobalCache: true
, only in this specific mode will trigger the error.4.2.1
to4.3.0-beta.1
$ yarn && yarn dev
The step 5 can successfully launch dev server in
4.2.1
but not4.3.0-beta.1
System Info
Used Package Manager
yarn
Logs
Logs are provided below
Click to expand!
Validations
The text was updated successfully, but these errors were encountered: