HEhex13·Apr 24, 2016
Interesting.
I have also seen other solutions which address this problem:
1. https://github.com/facebook/fbjs
library that Facebook uses in React: you have @providesModule annotations in modules, and you can write e.g. require('myModule') even if myModule.js is somewhere deep in directory hierarchy.
2. webpack configuration (e.g. you can write own loader to be able to make:
require('somethingWeird'), or probably use resolve like in this article: https://medium.com/@ericclemmons/dogfooding-your-open-source...
I mean, I don't want to underestimate your project by writing that something similar existed. Quite the opposite. I think that you made library for solving important problem (resolving dependencies in nice manageable way). I am just agnostic about which solution is the best.
Although I hope that in future one solution will prevail (ma
Read the rest
ybe yours, maybe webpack based, maybe @providesModule, or maybe this kind of functionality should belong to JavaScript language itself? Maybe ES8 or ES9 will have something like this?).
Because dependency management is too important for allowing to further fragmentation :)