4 ms·
Well written article. With Rails, though, you don't need to worry about any of this. Just define your modules and add controllers/services/directives/whatever
by ahuth 12y ago
Well written article.
With Rails, though, you don't need to worry about any of this. Just define your modules and add controllers/services/directives/whatever to them as needed using as many files as you want, and it just works. No module loading required.
Sorry for my ignorance, but does Node have something similar to Sprockets/The Rails Asset Pipeline?
- jaredmcateer 12y agoYes it does, plenty of options in fact, but as far as I can tell there is nothing in this article tying it to a particular backend
- burke_holland 12y agoSomebody commented about ASP.NET MVC having a bundler that you can just point at a directory. Seems like that would be enough to do it and you wouldn't need CommonJS or AMD.
- thoughtpalette 12y agoI think it depends on the framework.
- Touche 12y agoYour front-end application shouldn't be tied to what back-end technology you've chosen.
- aeflash 12y agoSprockets is incredibly primitive compared to something like RequireJS or Browserify -- all it does is concat. One might argue that Browserify is that JS bundler for Node. The issue is that using it with Angular seems superfluous because Angular has its own module system that works well when you just concat everything.