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
Please be advised that while we do not disallow extending and customizing the Webpack configurations these are not supported by the Angular tooling team.
This is also unlikely to be caused by the Angular CLI as we don't have any handling of graphql files. Please feel free to re-open the issue if you discover otherwise.
🐞 Bug report
Command (mark with an
x
)Is this a regression?
Yes, my custom build step works flawlessly in Angular v10.
Description
I just switched to Webpack 5 (Angular 11) and I now get 1 warning per .graphql file:
Nothing fancy with my setup I think, just this webpack extra config:
My graphql files don't import themselves or other files. Just simple graphql queries & mutations.
The warnings are there, but the app works well nonetheless.
Cross-posted here: apollographql/graphql-tag#326
🌍 Your Environment
The text was updated successfully, but these errors were encountered: