During my work on web project for US client, I faced with interesting issue, which at the first look seemed to be related to D3.js/C3.js donut charts, but after deep debugging, I discovered it’s because of nature of Underscore.JS 1.6.0 library/code. I would say, it’s bright example of the fact how important to know main purpose of dedicated API/tool, and implement custom codebase for the future to be working also correct.
It’s quite simple example I have experienced recently. But I think to share notes on blog, so that I remember this case and maybe someone else might use it in future.
The fact is – Lodash.JS is nice competitor for Underscore.JS. There are so many thoughts in a community regarding how different and how good they are. This post is about Backbone.JS and required dependency of Underscore and my willingness to BE SURE, that replacement/migration is OK. So I asked myself:
How good Lodash is against Underscore in scope of Backbone.JS stable/correct work?
And as turned out, I found more than answers, I found “future”. 🙂
Compare all managers how they allow to create packages. From that point, that you what to build your project in package manner.