Webpack 2, RC 4

#1

Post by jfmercer » Fri, Jan 13, 2017, 3:25 PM UTC

Re: Webpack 2, RC 4

#2

Post by jfmercer » Fri, Jan 13, 2017, 3:26 PM UTC

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."

Re: Webpack 2, RC 4

#3

Post by k__ » Fri, Jan 13, 2017, 4:16 PM UTC

I tried the dynamic import/require once and it was really nice.

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.

Re: Webpack 2, RC 4

#4

Post by VMG » Fri, Jan 13, 2017, 4:16 PM UTC

Aaaand github unicorns..

Re: Webpack 2, RC 4

#5

Post by Turbots » Fri, Jan 13, 2017, 4:18 PM UTC

VMG wrote: post #4

Aaaand github unicorns..

jep Github is down

Re: Webpack 2, RC 4

#6

Post by vanni » Fri, Jan 13, 2017, 4:24 PM UTC

VMG wrote: post #4

Aaaand github unicorns..

"We are currently experiencing major service outages."

https://twitter.com/githubstatus/status/819940738452615168

Hilarious replies on Twitter.

Re: Webpack 2, RC 4

#7

Post by AznHisoka » Fri, Jan 13, 2017, 4:28 PM UTC

Looks like there is some connectivity issues in OVH as well.. not sure if related?

Re: Webpack 2, RC 4

#8

Post by seniorsassycat » Fri, Jan 13, 2017, 5:44 PM UTC

I recently setup a typescript > webpack project and I was really disappointed with the dev-tools debugging experience.

Webpack renames imported bindings, so

        import {foo} from './bar';

becomes something like this

        let __webpack_require_foo_bar = _webpack_modules[5 /* foo */].bar;

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.

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.

Re: Webpack 2, RC 4

#9

Post by [deleted] » Fri, Jan 13, 2017, 5:53 PM UTC

seniorsassycat wrote: post #8

I recently setup a typescript > webpack project and I was really disappointed with the dev-tools debugging experience. Webpack renames imported bindings, so import {foo} from './bar'; becomes something like this let __webpack_require_foo_bar = _webpack_modules[5 /* foo */].bar; 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 s…

[deleted]

Re: Webpack 2, RC 4

#10

Post by johnny_reilly » Fri, Jan 13, 2017, 6:16 PM UTC

seniorsassycat wrote: post #8

I recently setup a typescript > webpack project and I was really disappointed with the dev-tools debugging experience. Webpack renames imported bindings, so import {foo} from './bar'; becomes something like this let __webpack_require_foo_bar = _webpack_modules[5 /* foo */].bar; 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 s…

One of the maintainers of ts-loader here. Debugging original source is totally possible. Take a look at the setup here: https://github.com/TypeStrong/ts-loader/tree/master/examples...

And in the official samples (WebPack 1): https://github.com/Microsoft/TypeScriptSamples/tree/master/r...