error bundling with rollup 0.36.1 about d3-hierarchy HOT 2 CLOSED

Sorry, but this isn’t enough information for me to investigate. What is the entry point to the bundle? The code you’ve included doesn’t look valid, because it’s calling the treemap constructor and then discarding the result. Probably the error lies in other code, most likely the root node you’re passing to the treemap instance.

When reporting an issue, please include a link to a live example, preferably on bl.ocks.org or RunKit, or as a pull request in the appropriate repository with new unit tests, that demonstrates that the described behavior is not the expected behavior. Use only the minimum amount of code necessary to reproduce the unexpected behavior.

A good bug report should isolate specific methods that exhibit unexpected behavior and precisely define how expectations were violated. What did you expect the method or methods to do, and how did the observed behavior differ? The more precisely you isolate the issue, the faster I can investigate.

Non-actionable bugs may be temporarily closed until you provide additional information. If you can’t isolate the bug any further, please let me know and I will try to help. However, I beg your patience: I must balance your request against many other responsibilities—fixing other bugs, answering other questions, new features, new documentation, etc. Please also consider asking for help on Stack Overflow.

If you have a question about D3’s behavior and want to discuss it with other users, also consider the d3-js Google Group or joining the d3-js Slack.

Thank you! 🤗

from d3-hierarchy.

Fair enough. I can't imagine how much you must be bombarded every day with crap posts. Sorry to add to the clutter.

I've created a self-contained repo that shows the error: https://github.com/davelandry/rollup-d3

The only thing I can think of that I forgot to mention in the initial post is that I'm using rollup-plugin-node-resolve. At the risk of cross-pollonation, I've also posted this issue in the rollup repository (as I'm starting to think that may be the culprit): rollup/rollup#1009

from d3-hierarchy.