yyx990803/rollup-tostringtag-symbol-conflict — explained in plain English
Analysis updated 2026-07-17 · repo last pushed 2021-02-22
Check if your custom classes using toStringTag symbols behave incorrectly after bundling with Rollup.
Use this repo as a reference case when reporting a similar object type-identification bug to Rollup maintainers.
| yyx990803/rollup-tostringtag-symbol-conflict | algorave-dave/fail-safe | avaritiachaos/qoder-proxy | |
|---|---|---|---|
| Stars | 22 | 22 | 22 |
| Language | JavaScript | JavaScript | JavaScript |
| Last pushed | 2021-02-22 | — | — |
| Maintenance | Dormant | — | — |
| Setup difficulty | easy | easy | moderate |
| Complexity | 1/5 | 1/5 | 3/5 |
| Audience | developer | general | developer |
Figures from each repo's GitHub metadata at analysis time.
The README is empty, so details come from the repo name alone, check the GitHub issues for the actual problem and fix.
A near-empty repo, likely a bug report, documenting a conflict between Rollup, a JavaScript bundler, and the toStringTag symbol used to control how objects report their type.
Mainly JavaScript. The stack also includes JavaScript, Rollup.
Dormant — no commits in 2+ years (last push 2021-02-22).
No license information is mentioned in the explanation.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.