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
On a similar note as #193, should we extends keepAssets to more than just CSS?
Thinking of importing static assets like images, which people can do with some custom webpack module rule, or at least when the Asset Import RFC lands. With the default config now, this won't work, as those files would not make it into the /dist build.
Is there actually a good reason to be restrictive here? Having stuff in the output is still pay-as-you-go, so when something extraneous gets there that is never imported, nothing bad will really happen - except for a bit more waste in node_modules, but we already have enough of that 😅
The text was updated successfully, but these errors were encountered:
On a similar note as #193, should we extends
keepAssets
to more than just CSS?Thinking of importing static assets like images, which people can do with some custom webpack module rule, or at least when the Asset Import RFC lands. With the default config now, this won't work, as those files would not make it into the
/dist
build.Is there actually a good reason to be restrictive here? Having stuff in the output is still pay-as-you-go, so when something extraneous gets there that is never imported, nothing bad will really happen - except for a bit more waste in
node_modules
, but we already have enough of that 😅The text was updated successfully, but these errors were encountered: