-
This is for a library with named exports and with no external dependencies. The repo is here: https://github.com/sidewayss/rAF I started with this stackoverflow question, then moved to this one. Now I know for certain that at least one of these names, These are the names that Rollup considers previously declared globals:
I can't find any docs that mention the other three as preset globals. I thought the solution would be @rollup-plugin-inject, based on this stackoverflow answer by @Rich-Harris. Now that I look at the plugin though, I don't think it solves my particular problem. I need a blacklist of names to not modify, or some other solution. Maybe I can work around it with the @rollup/plugin-replace? Not sure when that does its replacing, before or after the Why does Rollup consider these names to be previously declared globals? Or is there another reason for the suffixing? Any suggestions for working around this? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Turns out Rollup was just guiding me to remove circular import dependencies and find as-yet-untested, just-in-time compile errors waiting to happen. Removing circular dependencies cleared up most of the problem. |
Beta Was this translation helpful? Give feedback.
Turns out Rollup was just guiding me to remove circular import dependencies and find as-yet-untested, just-in-time compile errors waiting to happen. Removing circular dependencies cleared up most of the problem.
import {name} from "...";
cleared up the rest.