Imported default symbol names can conflict with a module’s internal symbols. about rollup

[mbostock]

Actually, it doesn’t have anything to do with the file names. Here’s another example:

foo.js:

function thing() {
  return "I am thing!";
}

export default function() {
  return thing();
};

bar.js:

import thing from "./foo";

thing();

This has the same problem. I can work around by renaming thing in foo.js to thing_foo or thing in bar.js to thing_bar.

[caridy]

a couple of notes here:

• default function should be hoisted in case some other module imported it in a circular fashion.
• synthetic identifier for a default export function, or class, should probably be named accordingly, something like: _foo_$default_ or something like that, to avoid collision with named exports in the same module.

[mbostock]

Thanks for the fast fix.

[Rich-Harris]

No problem - released as 0.8.1. @caridy Thanks for spotting that subtle point re hoisting - the new behaviour is that anonymous function expressions are converted into named function declarations (I figured that was easier than worrying about manually hoisting the definition).

[caridy]

👏