Named re-exports tree shaking?

[HanabishiRecca]

Sorry if the problem was already discussed, not found it here in the issues.

Example code:

index.js

import { submodule } from './lib';
submodule.foo();

lib.js

export * as submodule from './submodule';

submodule.js

export const foo = () => {};
export const bar = () => {};
export const baz = () => {};
export const whatever = () => {};

Output (--bundle --format=esm):

var __defProp = Object.defineProperty;
var __export = (target, all) => {
  for (var name in all)
    __defProp(target, name, { get: all[name], enumerable: true });
};

// submodule.js
var submodule_exports = {};
__export(submodule_exports, {
  bar: () => bar,
  baz: () => baz,
  foo: () => foo,
  whatever: () => whatever
});
var foo = () => {
};
var bar = () => {
};
var baz = () => {
};
var whatever = () => {
};

// index.js
submodule_exports.foo();

I think you understand the problem here. Is it possible to eliminate the dead code?

[evanw]

I believe this is a duplicate of #1420. Lack of tracking of exports through multiple levels of re-exports is a known limitation of esbuild. It's not possible to use esbuild to eliminate this as dead code.

[HanabishiRecca]

Oops, indeed a duplicate. Thanks for the answer.