[FeatureRequest] reproducable build among npm and pnpm

[loynoir]

Brief

When using package manager pnpm, compare with npm.
esbuild --bundle reproduce different output.

npm

// node_modules/fetch-blob/streams.cjs
var require_streams = __commonJS({
  "node_modules/fetch-blob/streams.cjs"() {
    // code
  }
});

pnpm

// node_modules/.pnpm/[email protected]/node_modules/fetch-blob/streams.cjs
var require_streams = __commonJS({
  "node_modules/.pnpm/[email protected]/node_modules/fetch-blob/streams.cjs"() {
    // code
  }
});

[loynoir]

pnpm: Fast, disk space efficient package manager

repo: https://github.com/pnpm/pnpm
install: https://pnpm.io/installation

[evanw]

The file path is the file path, and is not in esbuild's control. Non-minified output deliberately includes the file path because it's intended for debugging by a human. You will get different file paths with other different package managers too such as Yarn, which puts files inside zip files.

Relative file paths of input files are also included in the hashes present in output file names (a critical correctness feature for bugs such as #928), so even removing the file path comments and strings in the output files that you are pointing to does not guarantee reproducible builds.

Basically this is by design. Builds are only reproducible given the same file system contents. Use the same package manager if you want the same build output.

[hyrious]

You can use --minify-identifiers to remove the file path string in output.

[loynoir]

You can use --minify-identifiers to remove the file path string in output.

@hyrious Seems not working on v0.12.17. I try --minify-whitespace, that works, thanks!

[loynoir]

@evanw

Maybe provide --minify-path, for compactible build?
Is that possible?

[evanw]

I'm closing this as "by design" as described above. The file structure is part of the input, and different inputs lead to different outputs.