-
Notifications
You must be signed in to change notification settings - Fork 53
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
inconsistent es6/commonJs in Fragments? #271
Comments
If you are using template tags we need an inline |
If the require is necessary can the exports be made to be commonjs instead? |
im not recalling what a templateTag is |
By the way, this shouldn't be a problem with webpack5, I have an webpack 5 website deployed that works fine. What is your configuration? |
Hi Jaap |
(Not a pressing issue, but I would love to never see webpack again, personally) |
ahh! templateTagIsFunction! found it |
Hi Jaap et al.
My coworker points out that the generated code for a fragment file (at least) uses require to bring in @apollo/client but exports using es6 style.. This seems to be a problem for webpack...5?
Any tips or plans to square that up? any way I can help?
Thanks
Alex
@cid8600 @mattloomis
The text was updated successfully, but these errors were encountered: