4 ms·

Webpack 2, RC 4

64 points by jfmercer 10y ago

jfmercer 10y ago
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."
k__ 10y ago
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.
- simplify 10y ago
  That almost sounds like server-side rendering :)
  - patates 10y ago
    But SSR means you send everything around the content again and again.
    - simplify 10y ago
      If each page has different dependencies, you're not sending much duplicate content. Also, SSR supports incremental rendering (due to HTTP streaming), something that is currently impossible to do with SPAs. See this article for more detail: https://jakearchibald.com/2016/fun-hacks-faster-content/ https://jakearchibald.com/2016/fun-hacks-faster-content/
VMG 10y ago
Aaaand github unicorns..
- Turbots 10y ago
  jep Github is down
- vanni 10y ago
  "We are currently experiencing major service outages." https://twitter.com/githubstatus/status/819940738452615168 https://twitter.com/githubstatus/status/819940738452615168 Hilarious replies on Twitter.
AznHisoka 10y ago
Looks like there is some connectivity issues in OVH as well.. not sure if related?
seniorsassycat 10y ago
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.
- deleted 10y ago
  [deleted]
- johnny_reilly 10y ago
  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/webpack2-gulp-react-flux-babel-karma https://github.com/TypeStrong/ts-loader/tree/master/examples... And in the official samples (WebPack 1): https://github.com/Microsoft/TypeScriptSamples/tree/master/react-flux-babel-karma https://github.com/Microsoft/TypeScriptSamples/tree/master/r...
  - seniorsassycat 10y ago
    So I did reference those examples when I setup this project, but this doesn't have to do with typescript, or ts-loader. Here's some gists showing a minimal reproduction without typescript. https://gist.github.com/anonymous/ad044363f73b845cccb4e7f2259ac398 https://gist.github.com/anonymous/ad044363f73b845cccb4e7f225... Specifically, look at lines 25 and 28 of lib-main.js
    - johnny_reilly 10y ago
      Your WebPack.config.js appears to be missing this: devtool: 'inline-source-map' No sourcemaps, no debugging original source. Hope that helps

64 points by jfmercer 10y ago

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

k__ 10y ago

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.

simplify 10y ago
That almost sounds like server-side rendering :)
- patates 10y ago
  But SSR means you send everything around the content again and again.
  - simplify 10y ago
    If each page has different dependencies, you're not sending much duplicate content. Also, SSR supports incremental rendering (due to HTTP streaming), something that is currently impossible to do with SPAs. See this article for more detail: https://jakearchibald.com/2016/fun-hacks-faster-content/ https://jakearchibald.com/2016/fun-hacks-faster-content/

VMG 10y ago

Aaaand github unicorns..

Turbots 10y ago
jep Github is down
vanni 10y ago
"We are currently experiencing major service outages." https://twitter.com/githubstatus/status/819940738452615168 https://twitter.com/githubstatus/status/819940738452615168 Hilarious replies on Twitter.

AznHisoka 10y ago

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

seniorsassycat 10y ago

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.

deleted 10y ago
[deleted]
johnny_reilly 10y ago
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/webpack2-gulp-react-flux-babel-karma https://github.com/TypeStrong/ts-loader/tree/master/examples... And in the official samples (WebPack 1): https://github.com/Microsoft/TypeScriptSamples/tree/master/react-flux-babel-karma https://github.com/Microsoft/TypeScriptSamples/tree/master/r...
- seniorsassycat 10y ago
  So I did reference those examples when I setup this project, but this doesn't have to do with typescript, or ts-loader. Here's some gists showing a minimal reproduction without typescript. https://gist.github.com/anonymous/ad044363f73b845cccb4e7f2259ac398 https://gist.github.com/anonymous/ad044363f73b845cccb4e7f225... Specifically, look at lines 25 and 28 of lib-main.js
  - johnny_reilly 10y ago
    Your WebPack.config.js appears to be missing this: devtool: 'inline-source-map' No sourcemaps, no debugging original source. Hope that helps