CSS-in-JS: Would you trade the ability to have dynamic styles (any expression in CSS rules) for the benefit to compile CSS-in-JS to a static CSS file as build step? You would be disallowed to do css .thing { width: ${Math.random()*100}px but still could do css .thing { width: ${props.big ? 100 : 50}px . For this you get the benefits of static CSS: No runtime, easy SSR, no double parsing.

It seems pretty slow. I know. Please only use it when bundling for production. It'll compile each stylesheet twice by default ;)

I don't know how how HMR with figwheel works, but Amok is a great addition to the live update ecosystem. It work fundamental different than webpacks HMR. Amok uses the Chrome API to update code in place. It work at a very low level of the JS runtime. webpacks HMR is a pure JS solution, which is browser independent. Will Webpack update the HMR in the future? Currently I see to need to change HMR. It's working fine and I like it as pure JS solution.

multiple bundles? yes. You can pass multiple entry points to webpack and it'll generate multiple bundles which can be used on different HTML pages. But it would be better to design github.com as SPA with routing and SSR, it would be much faster...

What are some cool webpack features you love, but aren't being used by others actively? The target option. Compile to node.js and hot update your node.js application. That HMR can be used in production too (Would really love to see someone doing this). The chunk optimization plugins Any cool webpack tricks that most beginner/intermediates tend to overlook? 90% of the features. Code Splitting, MultiCompiler, [chunkhash] , Records are propably the most important ones.

Sublime (without vim bindings ;) )

How paths are resolved and in which order resolve.root => resolve.moduleDirectories => resolve.fallback How to make simple import works without using relative syntax resolve.root , resolve.alias in webpack.config.js or since webpack 2 concord.modules in package.json How inclusions and exclusions work for loaders A module is processed by a loader when it's matches any item in test and matches any item in include and doesn't match any item in exclude How does a .babelrc file in dependencies work when that dependency is being compiled by babel from another project That's not related to webpack but to babel. Starting from the compiled file the next .babelrc file when going up the hierachy is used. (As far as I remember). What needs to be an absolute paths and what need to be a relative path absolute: context , output.path , strings in module.loaders.test/include/exclude , strings in module.noParse , *resolve.root , *resolve.fallback , resolve.modules , recordsPath , recordsInputPath , recordsOutputPath relative or filename: resolve.moduleDirectories , output.filename , output.xxxFilename , resolve.modules , filename of extract-text-webpack-plugin , filename of SourceMapPlugin , filename of CommonsChunkPlugin url: output.publicPath module request: entry , values in resolve.alias basically: path means absolute, filename means relative

I cannot give a good advice here. It's an issue that will be tackled with concord, but that's not done. You can try to resolve the paths with enhanced-resolve like this: var resolve = require ( "enhanced-resolve" ).create.sync({ ...resolvingOptions, // same as webpack resolveToContext: true }).bind( null , __dirname); include : [ resolve( "some-module" ), resolve( "another-module" ) ] never tried this, but it's an idea.

Really cool. I'm still shocked by the success. Thanks to Pete Hunt. But at the same time I'm a bit sad because I can't dedicate more time to webpack. There is so much we can do we would have more time.

I like React, Redux, CSS Modules, Babel. I like the ideas of TypeScript and Relay, but don't use them because of the implementation architecture quality. Looks like they were not implemented by web people... React because of immutable and declarative. Some for Redux. CSS Modules because of webpack and modularity. Babel because because I don't like the TypeScript implementation. And I really like flexbox. So cool ;)