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.
@bluwy problem occurs when you have monorepo. For example: 1 package with ui components, 2 package is app.
When you stat app with dev server and open page from firefox - you get: Loading failed for the module with source “http://localhost:5173/@fs/path_to_package1/filename.js”.
@bluwy problem occurs when you have monorepo. For example: 1 package with ui components, 2 package is app. When you stat app with dev server and open page from firefox - you get: Loading failed for the module with source “http://localhost:5173/@fs/path_to_package1/filename.js”.
Thanks @numfin , can you explain more? Are you saying this is an issue anytime there's more than one "entry"?
@jordanade i'm not sure. I just have monorepo project and when i open main app with imported component library - i get this err in firefox
(just reporting the problem, not solving it)
Describe the bug
Running VITE v5.4.7 and LARAVEL v10.48.22 (plugin v1.0.5). Running "npm run dev". Using Firefox 130 on Mac. Using about 40 inputs.
Page loads only work roughly half the time. Often one or more modules will fail to load. Seems to happen more on initial page load but not always.
Console shows "Loading failed for the module with source XXX". Network inspector shows modules failed with NS_ERROR_NET_PARTIAL_TRANSFER error.
Works fine on Chrome.
Reproduction
I can't do this at the moment (understand this is a problem) but wanted to put this issue in so others could find it.
Steps to reproduce
Run dev server with many inputs configured, open in Firefox.
System Info
Used Package Manager
npm
Logs
Nothing out of ordinary seen in logs when errors occur
Validations
The text was updated successfully, but these errors were encountered: