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
There's a critical issue where the @hubai/core package is being loaded twice when extensions use relative imports in the format of @hubai/core/esm/...
This redundancy in loading can lead to performance inefficiencies and unexpected behaviors in the application.
Temporary Workaround:
Until this issue is resolved, it's recommended for all extensions to strictly use absolute imports. For example, use import { X } from '@hubai/core' instead of relative import paths.
Steps to Reproduce:
Include an extension that utilizes relative imports from the @hubai/core package (e.g., @hubai/core/esm/foo-bar).
Observe that the @hubai/core package is loaded twice in the network tab.
Expected Behavior:
The package should only be loaded once, regardless of the import method used in extensions.
Actual Behavior:
The package is loaded twice when relative imports are used in extensions.
I'm still trying to find a solution to this problem, if you have any suggestions please comment below.
In the meantime, we appreciate your cooperation in using absolute imports to avoid this problem.
The text was updated successfully, but these errors were encountered:
There's a critical issue where the @hubai/core package is being loaded twice when extensions use relative imports in the format of
@hubai/core/esm/...
This redundancy in loading can lead to performance inefficiencies and unexpected behaviors in the application.
Temporary Workaround:
Until this issue is resolved, it's recommended for all extensions to strictly use absolute imports. For example, use import { X } from '@hubai/core' instead of relative import paths.
Steps to Reproduce:
Include an extension that utilizes relative imports from the @hubai/core package (e.g., @hubai/core/esm/foo-bar).
Observe that the @hubai/core package is loaded twice in the network tab.
Expected Behavior:
The package should only be loaded once, regardless of the import method used in extensions.
Actual Behavior:
The package is loaded twice when relative imports are used in extensions.
I'm still trying to find a solution to this problem, if you have any suggestions please comment below.
In the meantime, we appreciate your cooperation in using absolute imports to avoid this problem.
The text was updated successfully, but these errors were encountered: