Named default import symbols get incorrectly renamed

[seivan]

There seems to be a distinction between the names of an exported value between deno run and deno compile when importing an object and using it as a key in a new object

In 'https://deno.land/x/yargs_parser@v20.2.4-deno/deno.ts'

export default yargsParser

In 'https://deno.land/x/yargs/deno.ts'

import Parser from 'https://deno.land/x/yargs_parser@v20.2.4-deno/deno.ts';

const newObject = {
 Parser
}

This will create {yargParser: Parser} in deno compile which is unexpected.

Expected value would be {Parser: Parser} which is the result you get with deno run

Related: yargs/yargs#1891

[kitsonk]

What problem is this causing?

When you bundle ESM modules, some renaming has to take place. Modules are bundled before they can be used in deno compile.

[seivan]

@kitsonk Sorry for being unclear, I rephrased the issue.
The expectation is that this should work

const someObj = {
 Parser
 }
 
 assert(someObj.Parser)

both in deno run and deno compile

[kitsonk]

cc/ @kdy1

Looks like some default import symbols get renamed, which then causes unexpected/breaking changes in the downstream code.

[nayeemrmn]

Occurs with any aliased imports:

import { foo } from './temp2.ts';

console.log({
  foo
});

// temp2.ts
const bar = 1;
export { bar as foo };

Bundle output:

console.log({
    bar: 1
});

Expected:

console.log({
    foo: 1
});

SWC should ensure { foo } is treated the same as { foo: foo }.

[kdy1]

Fixed on upstream. (Published a new version)

[bartlomieju]

Fixed in 1.9.0