-
Notifications
You must be signed in to change notification settings - Fork 787
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tries to import from unavailable chunk #618
Comments
@bitflower So the repro case here is to import a module into two separate components correct? |
Hey, exactly, but maybe it depends on the imported module (in this case Feathers). But as a start it would be the same mod imported into 2 components, yes. Sorry didn't prepare this. Will you? Lemme know if we should chat on Slack... |
As you can see in the pic Stencil is trying to import from chunk9 which is obviously not loaded on the left side (?) |
I have prepared a private repo showcasing the issue. Who should I add as collaborator? You, @jgw96 or someone else? EDIT: I have added you for now. The branch is "data_component" located here: |
This seems to work in 0.7.2! Is this on purpose or random? Thanks for your continuous updates! |
Great! We recently updated the version of Rollup so most likely it was fixed. |
Stencil version:
I'm submitting a:
[ x ] bug report
Current behavior:
There's a reference to a non existing chunk file in the component file which causes
is not defined
errors when (lazy) loading the component:The error:
It started to occur when I imported the same module the second time in another component. As long as I only use the module in one component all is working fine.
Expected behavior:
A "shared" module can be used in multiple components without errors.
Steps to reproduce:
That's the thing. The setup of the project is quite overwhelming (including backend dependency without which the code will not work). I would agree to grant access to the private repo though as I'm very much interested in
a) solving this for me and
b) stick with (super-duper) Stencil and
c) it is related to a very profilic npm module (FeathersJS)
The text was updated successfully, but these errors were encountered: