Man, the grammar in the article is pretty bad...
Anyway, I don't think I'll use it until it'll have tree-shaking, but kudos for the effort. Creating a (decent) modern bundler isn't an easy task at all.
Ah, and another thing: referencing the project's root with "~". Really not a fan of it. I won't probably never load a module from the home directory, but this is messing with a widely estabilished convention.
I'm relatively sure the author has exposure to .Net as the tilde is used as project root the too. It doesn't work out autosub for profile/home in node currently in any of the path or FS modules.
I know... I work with Windows, Linux and Mac on a daily basis. I was just pointing it out in context as to why that was chosen. It *could* also be thought of as the *home* for the application itself.
I even mentioned that node specifically doesn't do anything with tilde in the fs or path modules, even in a unixy environment.
thank man for the support :) that is exactly why we chose it. because we come from.Net background.
to answer the OP, try to check how many npm packages like `app-root-path` are trying to solve this big issue and you will get a better idea about the reasoning behind it.
A lot of negativity here, which bums me out. I think Fusebox looks really promising and I'm definitely going to consider it for future projects as a means of sidestepping webpack's complexity.
1) We support HMR
2) We have different approaches.You can split your code as much as you like, creating bundles using arithmetic instructions http://fuse-box.org/#arithmetic-instructions
3) WebPack tree-sharking works poorly. We are working on a universal solution that will support CommonJS tree-shaking.
Hello!
No, We are not confusing it with anything.
There is a great PR going on. We are going to introduce HMR plugins, that will allow users to specify their own logic. Without altering the code.
https://github.com/fuse-box/fuse-box/pull/158