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
Is your feature request related to a problem? Please describe.
In our project, we are using the entrypoints option set to true to organize el assets output by entry points so we can load the proper assets for each page. We would like to preload the font assets, which aren't in any chunk due to being imported in scss files. Those assets are part of the "unnamed chunk" which is included in the assets file when entrypoints is false.
Describe the solution you'd like
We would like to include a new option called includeFilesWithoutChunk which is false by default and when set to true, the assets from the "unnamed chunk" would get included in the assets file under a "unnamed key" in the json output.
Describe alternatives you've considered
We haven't think of other alternatives for solving this problem. Suggestions are welcome.
Additional context
We are testing this change on a fork that we included in our project. The code change diff looks like this:
If this solution is accepted, I can create a PR with this code to this repo.
Thanks!
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In our project, we are using the
entrypoints
option set to true to organize el assets output by entry points so we can load the proper assets for each page. We would like to preload the font assets, which aren't in any chunk due to being imported in scss files. Those assets are part of the "unnamed chunk" which is included in the assets file whenentrypoints
is false.Describe the solution you'd like
We would like to include a new option called
includeFilesWithoutChunk
which is false by default and when set to true, the assets from the "unnamed chunk" would get included in the assets file under a "unnamed key" in the json output.Describe alternatives you've considered
We haven't think of other alternatives for solving this problem. Suggestions are welcome.
Additional context
We are testing this change on a fork that we included in our project. The code change diff looks like this:
If this solution is accepted, I can create a PR with this code to this repo.
Thanks!
The text was updated successfully, but these errors were encountered: