Skip to content
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

Unable to use default/wildcard import #371

Open
leoadamo opened this issue Feb 3, 2023 · 0 comments
Open

Unable to use default/wildcard import #371

leoadamo opened this issue Feb 3, 2023 · 0 comments

Comments

@leoadamo
Copy link

leoadamo commented Feb 3, 2023

Hello @tusbar, hope you are fine!

I am using this plugin in a gulp-based project, and it would be useful to import all .env variables together, for example:

import myEnvConfig from “@env”;

Also, I’ve tried to use a wildcard import, like this:

import * as myEnvConfig from “@env”;

But it seems like wildcards are not supported too.

Current behavior:

When trying to use those approaches I receive an error in the console saying that default/wildcard exports are not supported by the module.

Thank you in advance guys!

@leoadamo leoadamo changed the title Unable to use named import without destructuring Unable to use default import Feb 3, 2023
@leoadamo leoadamo changed the title Unable to use default import Unable to use default/wildcard import Feb 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant