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
Currenly the (file: string, type: string) => boolean is TOO unmeaningful.
The file args in vite is the output chunk name, which is probably like index.html.xxxx.js.
It lost infoamtion about how it was generated, so users at this time have No idea about what's page is this chunk generated from. So it's impossible for a developer or a user to take actual effect when setting a function.
The parameters should be rebuilt. At least it should include:
chunk filename
chunk filetype (can be ommited if filename contains extension). Also I am confused why current api seperate a full chunk path into file name and file type.
chunk infomation about how this chunk is generated.
I feel the same way. Sometimes the file doesn't change, but once rebuild, a bunch of files change their names, and you can't find difference in different commits.
Clear and concise description of the problem
Currenly the
(file: string, type: string) => boolean
is TOO unmeaningful.The file args in vite is the output chunk name, which is probably like
index.html.xxxx.js
.It lost infoamtion about how it was generated, so users at this time have No idea about what's page is this chunk generated from. So it's impossible for a developer or a user to take actual effect when setting a function.
Just an example, I am getting hundreds of
index.html.xxxx.js
in https://github.com/vuepress-theme-hope/v2/tree/gh-pages/assets.Suggested solution
The parameters should be rebuilt. At least it should include:
chunk filename
chunk filetype (can be ommited if filename contains extension). Also I am confused why current api seperate a full chunk path into file name and file type.
chunk infomation about how this chunk is generated.
Could be things like:
Edited: In some cases we might get an array here, so we can use array formats.
Alternative
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: