3 ms·
I used requireJS for a project about a year and a half ago, and I agree that the documentation is not good. The error messages are also not good. When I couldn'
by badman_ting 13y ago
I used requireJS for a project about a year and a half ago, and I agree that the documentation is not good. The error messages are also not good. When I couldn't figure out the right way to configure something, I had to use trial and error. Basically, everything about using it kinda sucked, but we wanted the dependency resolution for our scripts.
I haven't looked into alternatives (mainly Browserify) and don't know if I will use JS modules in my future development. The idea seems neat, but it really adds a lot of pain in my opinion. Perhaps there is a threshold of webapp complexity, past which the pain is worth it.
- AdrianRossouw 13y agothis is my main problem with it. it's an astounding amount of complexity to introduce into a project, just to be able to get the bare minimum of functionality. if something breaks, and something always breaks, I simply don't want to be responsible for debugging it.