-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 3.0 #558
Comments
these changes won't break my build. |
Sounds like good changes, I agree with all of them 👍 . Let me know if you need any help with the changes, I might have some time next week. |
Better favicon support would be fantastic.
Em 23 de jan de 2017 21:18, "Kees Kluskens" <[email protected]>
escreveu:
Sounds like good changes, I agree with all of them 👍 . Let me know if you
need any help with the changes, I maybe have some time next week.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#558 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA-GqyHWGP4TigN3aTscvycEko19Ol5Oks5rVTUsgaJpZM4Lrp6G>
.
|
Would you consider discussion around migrating repo to github.com/webpack-contrib org? |
None of the changes will affect me. 👍
This was added via #311 (original issue: #309). As it turns out, the issue I originally reported was caused by the |
I'm looking forward to the feature of generating multiple html files. 👍 |
Generate multiple html files is a good feature! Include it with |
You know that you can generate multi html files by using multiple instances of |
Sure. I think it's not elegant if you using ten instances for ten pages. (Although you can use something like |
Only thing there that I'd need to make changes for is minifying, and I wholly support making a separate plugin for it. So 👍 from me! 😄 |
How about isomorphic support? I've been looking for an elegant solution about template reusability when I use server-rendering. Like the following (A rough example):A common template : template.ejs <!DOCTYPE html>
<html lang="en">
<head>
<title><%= htmlWebpackPlugin.options.title %></title>
</head>
<body>
<!-- Use a special format to pass server-rendering data? -->
<!--{{ serverRenderingData.body }} -->
<script src="<%= htmlWebpackPlugin.files.chunks.app.entry %>"></script>
</body>
</html> 2(kinds of) files are generated :
<!DOCTYPE html>
<html lang="en">
<head>
<title>title</title>
</head>
<body>
<script src="//example.com/publicPath/app.bundle.js"></script>
</body>
</html>
module.exports = function(serverRenderingData){
return `
<!DOCTYPE html>
<html lang="en">
<head>
<title>title</title>
</head>
<body>
${serverRenderingData.body}
<script src="//example.com/publicPath/app.bundle.js"></script>
</body>
</html>
`
}; Anyone has better practice? or any suggestion? |
I'm 👍 with all those changes as you are following semver so the impact can be managed easily. Thank you for including us in the discussion! |
|
thanks for all your feedback 👍 @spuf ava has build in support for |
@TheLarkInn probably a separate topic to V3.0: #565 |
Hi, if you choose to support multiple html files, can you ensure your events API supports this - don't know what mechanism you will choose but, e.g., ensure you pass through the entry point for that html file. |
@numical I'll try to keep it in my mind ;) |
WRT generating multiple files: I'm working with a static site generator (metalsmith) and using html-webpack-plugin to generate injected assets. However, because pages can be added or removed at "devtime", the plugin does not pick up these new files, requiring a full rebuild just to pick up the new file. Not sure what can be done here, but just chipping in. A single instance of the plugin that takes a glob and watches for changes may justify it as an enhancement. |
+1 waiting for entrypoints and several files. Good for building multipage applications! |
If you are looking for a workaround for the whole multipage I have something that wraps this plugin github.com/mutualofomaha/multipage-webpack-plugin that might help |
removing I'm currently having to use this snippet to make sure my bits are properly sorted: #481 (comment) |
please make dynamic entrypoints, for example:
|
Hi @jantimon will these be addressed soon? Now that 3.0 is out. |
Might be a good idea to remove chunkSortMode as an option from the documentation for version 3? |
Is this going to be done for v4? |
Because of the webpack 4 release those changes were postponed to html-webpack-plugin 4 Almost all features described above are implemented in #953 And are already published as alpha to npm: https://www.npmjs.com/package/html-webpack-plugin/v/4.0.0-alpha.2 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
At all contributors
@SpaceK33z, @SimenB, @numical, @kennyt, @okhomenko, @cgreening, @anjianshi, @mistadikay, @mc-zone, @JSteunou, @spuf, @vincentngthu, @NekR, @mateatslc, @chiplay, @ascariandrea, @graingert, @zzuieliyaoli, @foglerek, @sandeep45, @koenpunt, @sokra, @shprink, @cesarandreu, @oliviertassinari, @sebastienbarre, @jamesjieye, @AndrewRayCode, @kurtharriger, @ai, @PeachScript, @kinday, @TalAter, @chrillo, @timoxley, @insin, @adjohnson916, @Madalosso, @mgol, @victorwpbastos, @pburtchaell, @dtinth, @yyx990803, @michael-wolfenden, @denis-sokolov, @jirikolarik, @jpetitcolas, @ruehl, @Foxandxss, @creeperyang, @vyorkin, @thomasguillory, @tlrobinson, @nartamonov
I am planning to move the webpack-html-plugin forward to 3.0 and would like to gather your input which (breaking-)changes you would like to see
Planed changes:
stats.entrypoints
to determine which links/scripts should be added to the html. (Unfortunately this will stop the support for webpack 1 as @sokra won't port this feature back into webpack 1)type: 'text/javascript'
stats.entrypoints
are already sorted)Open for discussion:
ava
The text was updated successfully, but these errors were encountered: