3 ms·
What's even more confusing is that v3 -> v4 includes a bunch of breaking changes, and yet they didn't update their typescript definition file. Not to mention th
by hacker_9 8y ago
What's even more confusing is that v3 -> v4 includes a bunch of breaking changes, and yet they didn't update their typescript definition file. Not to mention the web is full of v3 examples that mysteriously don't work with your d3 lib (and versions are never mentioned anywhere).
- symlinkk 8y agoI've had no problem with TypeScript and D3. I'm using `@types/d3`, is that what you're using?
- mschuster91 8y ago> Not to mention the web is full of v3 examples that mysteriously don't work with your d3 lib Unfortunately this is widespread across the JS ecosystem. Hell I'm not saying anyone should do it like Linux (break userspace and get shot), but when one does backwards-incompatible changes, is it so hard to stub dead methods or unsupported calling ways with "console.error('Outdated, see https://github.com/x/y/issues/z');" https://github.com/x/y/issues/z');"?