Bug in path generation for code-split import paths

[ggoodman]

Description

outputs[*].inputs[].path values appear to include invalid directory segments when shared chunks are produced by nested paths.

Reproduction

The following is a mini example that reproduces what I'm observing. It has a single entrypoint, with two chunks dynamically imported. The two lazy chunks and the main entrypoint all share a dependency on ./shared.js.

./index.js

import './shared';
import('./pages/about'), import('./pages/home');

React.createElement('div');

./shared.js:

//Side-effect
console.log('Shared');

./pages/about.js:

import '../shared';

./pages/home.js:

import '../shared';

esbuild \
  --bundle \
  --format=esm \
  --define:process.env.NODE_ENV=\"production\" \
  --platform=browser \
  --outdir=build \
  --metafile=build/meta.json \
  --splitting \
  index.js

The issue can be observed in the following screenshot. Note that two output chunks refer to the same filename (chunk.3D7RKSRB.js), however at different locations. You can also see in the file tree that this chunk is only at the root of the build folder and is not duplicated in the build/pages folder.

[evanw]

Thanks for reporting this. The issue has been fixed and the fix will go out with the next release.