I recently setup a typescript > webpack project and I was really disappointed with the dev-tools debugging experience.<p>Webpack renames imported bindings, so<p><pre><code> import {foo} from './bar';
</code></pre>
becomes something like this<p><pre><code> let __webpack_require_foo_bar = _webpack_modules[5 /* foo */].bar;
</code></pre>
So if you are paused in the debugger and want to use foo in a watch statement, or use it in a computation you'll have to reference the real source instead of the source maps.<p>I found questions on SO, and it seems like a known and accepted problem, but I know I won't be able to sell my team on Webpack because of this.
According to sokra, this ought to be the final rc. From the release notes: "This is probably the last RC. We released it as final test. If no critial bugs are discovered, we release 2.2.0 in < 10 days."
I tried the dynamic import/require once and it was really nice.<p>I could just write a normal SPA and require some stuff in every route, so the client only downloads the code that is used for the current page and things worked fine without extras needed.