webpack is a bundler for modules. The main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable of transforming, bundling, or packaging just about any resource or asset.
Feel free to ask any high level questions about webpack. This is also a great opportunity for you to know more about the awesome developers who develop and maintain webpack.
Hosted by:
I had struggle using webpack with applications that are not SPA. The best example I can mention is github.com. It consists of many small SPAish applications. What strategy I have to follow to use webpack when developing these kind of applications? (multiple bundles?...)
As community members how can we help you guys keep contributing to webpack development? If you decide to start a kickstarter campaign, how soon will it be?
Thanks for your time guys. :) What editors do you use to write JavaScript code?
What are some cool webpack features you love, but aren't being used by others actively?
Any cool webpack tricks that most beginner/intermediates tend to overlook?
Hope you don't mind me asking multiple questions :D
How does it feel to be the creator of a widely used open source project like webpack?
Juho : What's the story behind SurviveJS? How did you come up with this plan?
What is the best way to specify that a loader should compile a dependency from npm and have that working with npm link? I see that there are some issues with path.join and path.resolve with the resolve and resolveLoader settings.
Do you work full time on webpack? Have you considered getting a company sponsor webpack development?
What is the use of devtool configuration option in webpack?
In terms of programming what else do you guys do apart from developing and maintaining webpack? How do you manage your time? What are your productivity hacks?
Can webpack be used as a build tool and replace gulp/grunt completely?
Is webpack-bootstrap outdated? It seems like it cannot find webpack-bootstrap in the global namespace
What's your advice to someone that never contributed to webpack before start doing it right now? Maybe documentation etc?
Is github.com/webpack/extract-text-webpack-plugin going to be improved? It seems pretty slow. We used that to compile .sass files. We do not use CSS modules. Building styles was taking up to 40 seconds. We ended up moving .sass compilation to gulp.
This is a simplified scenario that I think other people can relate to, and has the following properties:
shared-repo. shared-repo has its own dependencies on modules exclusive to the other 2 projects. transform-decorators-legacy and jsx-control-statements as plugins. babel-node that programmatically start webpack. It seems that the most effective way to have good development speed would be something like:
npm link for shared-repo shared-repo should be compiled with babel, the others modules should just be imported without compiling.shared-repo and the main repo.To me this scenario seems a simple one. If the assumption is that node_modules are compiled to ES5, ideally I would have like to just say in one line "use babel-loader for shared-repo but for no other dependencies".
When we were trying to implement this kind of workflow, it took a few days of trial and error. Most of the information we used to implement the solution was found in small parts of github issues. Our current webpack.config code for this setup takes up many lines, and even though it now works, we are unsure if it is overly-complicated or has undesired effects.
We think there are a number of sticking points. Firstly, resolve.modulesDirectories, resolve.fallback, resolve.root, resolveLoader.root, resolveLoader.fallback, module.loaders.include, module.loaders.exclude, externals interact with each others in as pipeline that we could not find documented to any large degree. The documentation provided seems to take these settings one-by-one, and often does not include examples of more complicated setups.
Secondly, we found the documentation very unclear for https://webpack.github.io/docs/resolving.html and webpack.github.io/docs/library-and-externals.html From reading issues on github and other resources it seems like other users of webpack are also confused.
A few things we would love to have covered in more detail:
import mod from 'shared-repo' vs import mod from '../../../../ shared-repo).babel-loader and what is not ).babelrc file in dependencies work when that dependency is being compiled by babel from another project (i.e. how can this file be ignored, for instance with with query?) path.join vs path.resolve) to makenpm link work with not only loaders, but also plugins.First, I would like to understand what is the ideal solution for this scenario
Second, we think that the webpack community would benefit from a bit better documentation of the above list.
Tobias, when are you planning to get yourself a Twitter account?
Elimination of dead code has been the biggest pain for me when it comes to developing web apps. Are there any guidelines that should be followed to keep redundant code to a minimum? Also, is there any parallel to tree shaking for CSS?
How do you feel about HTTP/2.0? Considering things like: the bundling stuff isn't so "necessary", etc.
How do you compare Webpack with JSPM? Do you think they are different tools for different purposes?
What's your advice for beginner JavaScripters who want to contribute something to webpack development?
Antoine Grant
Software Engineer @ The New York Times
Tobias Koppers
SurviveJS
Juho Vepsäläinen
SurviveJS
Tobias Koppers
Tobias Koppers
SurviveJS
Juho Vepsäläinen
SurviveJS
Antoine Grant
Software Engineer @ The New York Times
Would you recommend to use require hooks such as
css-modules-require-hook&babel-registeror would creating a server specific bundle would make more sense?