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
This is effectively a reversal of #1254 and #1257
This is desired because webpack and other plugins (e.g. workbox) doesn't do the encoding.
If html-webpack-plugin does the encoding, it could break other plugins.
For instance, when the backend server or server worker (e.g. one generated by workbox) is serving the generated JS files, it won't necessarily decode the URL before serving the file.
Since all npm packages have URL-safe names, I think it should be up to the users to ensure the entries are URL safe rather than letting the plugin does the encoding automatically.
The text was updated successfully, but these errors were encountered:
Current behaviour 💣
Chunk file name is URL encoded.
Expected behaviour ☀️
Chunk file name should not be URL encoded.
Reproduction Example 👾
Explanation
This is effectively a reversal of #1254 and #1257
This is desired because webpack and other plugins (e.g. workbox) doesn't do the encoding.
If html-webpack-plugin does the encoding, it could break other plugins.
For instance, when the backend server or server worker (e.g. one generated by workbox) is serving the generated JS files, it won't necessarily decode the URL before serving the file.
Since all npm packages have URL-safe names, I think it should be up to the users to ensure the entries are URL safe rather than letting the plugin does the encoding automatically.
The text was updated successfully, but these errors were encountered: