wtf is rollup-side-effect-bug?

This repository is a small test case that reproduces a specific bug in a popular JavaScript build tool called Rollup. The project exists to prove that something is going wrong when Rollup processes a package setting called sideEffects, which is a flag developers use to tell build tools which files in their project have meaningful side effects (like modifying global state) and which are safe to delete if unused. The repo is tied to a bug report filed by Mike Bostock, the creator of the D3 visualization library, on the Rollup GitHub page. To understand the problem, it helps to know that when you write JavaScript, you often import a lot of code you don't end up using. Modern build tools try to make your final file smaller by removing the unused parts, a process called "tree shaking." The sideEffects field in a project's configuration helps the build tool decide what it can safely remove without breaking the application. This test case demonstrates that Rollup is incorrectly deleting or altering code based on this flag, which can break a functioning application. A developer or project manager working on a JavaScript library, especially something visual like D3, would run into this issue when their build process unexpectedly breaks their code. By running a couple of simple commands, someone experiencing the bug can see the problem happen in real time. The project also includes a simple way to confirm the cause: if you remove the sideEffects declaration from the test package's configuration and run the test again, the problem goes away, proving that the flag is the culprit. The project itself is purely a diagnostic tool. It contains no features or application logic. Its sole purpose is to serve as a clear, reproducible example so the maintainers of Rollup can investigate and fix the underlying tree-shaking issue.