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
As discussed at length in #83, there is an inherit difference in workerd between modules that are actually imported and modules that are imported using eval inside runInlinedModule (which is needed for Vite's dev modules handling/abstraction).
This misalignment is something we should ideally document somewhere so that users could, if needed, be aware of it.
Footnotes
I think that we could in theory actually add some heavy handed hacks to manipulate the code to align the dev and production as closely as possible, but that would most likely be quite complex, brittle and overall not worth it, so I think we should really not consider it unless a very very strong argument is made for something like that ↩
The text was updated successfully, but these errors were encountered:
As discussed at length in #83, there is an inherit difference in workerd between modules that are actually imported and modules that are imported using
eval
insiderunInlinedModule
(which is needed for Vite's dev modules handling/abstraction).And it doesn't seem like we can align the two1.
This misalignment is something we should ideally document somewhere so that users could, if needed, be aware of it.
Footnotes
I think that we could in theory actually add some heavy handed hacks to manipulate the code to align the dev and production as closely as possible, but that would most likely be quite complex, brittle and overall not worth it, so I think we should really not consider it unless a very very strong argument is made for something like that ↩
The text was updated successfully, but these errors were encountered: