We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Stencil version:
@stencil/core@0.4.3
I'm submitting a:
Current behavior:
When importing a module from a component using wildcard syntax:
import * as someModule from './some-module'; @Component({ tag: 'my-component' }) export class MyComponent {
And using the import somehow in the render method:
render() { return <div>{ someModule.someProp }</div>; }
I get a runtime error: ReferenceError: someModule is not defined.
ReferenceError: someModule is not defined
Expected behavior:
The module should be bundled with the component? Would wildcard imports break code splitting? Using named imports works as expected:
import { someProp } from './some-module';
Steps to reproduce:
I've reproduced in this repo.
The text was updated successfully, but these errors were encountered:
256e70a
jthoms1
No branches or pull requests
Stencil version:
I'm submitting a:
Current behavior:
When importing a module from a component using wildcard syntax:
And using the import somehow in the render method:
I get a runtime error:
ReferenceError: someModule is not defined
.Expected behavior:
The module should be bundled with the component? Would wildcard imports break code splitting? Using named imports works as expected:
Steps to reproduce:
I've reproduced in this repo.
The text was updated successfully, but these errors were encountered: