Echo JS 0.11.0


faceyspacey 519 days ago. link 2 points
awesome stuff! I love FuseBox. Just an idea: at the top where u say "loves Typescript" it almost feels like Babel is left out. It might help for promotion to not leave the large React/Babel crowd out of the equation so early in the readme.
nchanged 519 days ago. link 1 point
It's the first class support, of course, we promote it. Making it easier to start with typescript!

And it's much faster. In 2.2.3-beta we have `useTypescriptCompiler` option, which allows you to transpile es6 code with typescript. 

Babel is not left out,

For example, is based on babel.
Hylix 521 days ago. link 2 points
Why keep posting this? Sure it's a nice piece of software but as long as there isn't anything new (blogpost or something) reposting the same github repo seems kinda useless..
nchanged 521 days ago. link 2 points
Keep posting? Last time a link was posted was like 10 month ago. And we've got a new stable release here.
Hylix 520 days ago. link 3 points
I am pretty sure in the meantime it has been posted, nonetheless in my opinion it would be cooler to see articles posted about what exactly is new about Fusebox instead of just a link to the repo.
bigopon 520 days ago. link 1 point
Well people here are supportive but more straightforward in wording than usual. Very nice work.
faceyspacey 519 days ago. link 1 point
also, would love to figure out how to get React Universal Component + webpack-flush-chunks running in Fusebox. Do you have any way to "weakly" require a dependency so it doesnt end up in the parent bundle. The equivalent of webpack's `require.resolveWeak`, or ideally: `require.requirewWeak`?

The idea is for code-split apps with SSR, you get the additional chunks to the client manually. But you still need to be able to reference them in the parent chunk, as sometimes they will be embedded in the page.
faceyspacey 506 days ago. link 1 point
what about synchronous resolution server-side? i.e. the require.resolveWeak stuff? ...i'd need to find a solution for that for Universal. Currently react-universal-component knows its running in webpack, and uses internal webpack methods to require "weakly" (i.e. without indicating to put the code split component into the parent bundle when the same code is run on the client).