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
I have an issue with auto import logic. I have storybook which is configured to a library type system. It automatically loads the systemjs like output bundle.
SystemJS has document readyState check, in case loading it would add module to a autoImportCandidates. Later on its used in a instantiate logic, so it skip module load. Because of it, getRegister is not executed and last register is not reset. It leads to a wrong dependency resolution of the first dependency of a module.
Example:
System.register(['react','react-dom'],()=>{...})
First module dependency react has a dependency ['react', 'react-dom']
Is it expected behavior ?
I guess lastRegister should be reseted on auto imported modules as well. It could be done right once autoImportCandidates is reseted.
The text was updated successfully, but these errors were encountered:
Question
I have an issue with auto import logic. I have storybook which is configured to a library type
system
. It automatically loads thesystemjs
like output bundle.SystemJS has document readyState check, in case
loading
it would add module to a autoImportCandidates. Later on its used in a instantiate logic, so it skip module load. Because of it, getRegister is not executed and last register is not reset. It leads to a wrong dependency resolution of the first dependency of a module.Example:
First module dependency
react
has a dependency['react', 'react-dom']
Workaround
Im hacking auto import logic, manually calling getRegister to reset lastRegister
Sumarry
Is it expected behavior ?
I guess lastRegister should be reseted on auto imported modules as well. It could be done right once autoImportCandidates is reseted.
The text was updated successfully, but these errors were encountered: