webpack sourcemap include absolute path

Bug report

What is the current behavior?

If the current behavior is a bug, please provide the steps to reproduce.

https://github.com/xiaoxiangmoe/webpack-source-absolute-path-bug

• git clone https://github.com/xiaoxiangmoe/webpack-source-absolute-path-bug.git
• cd webpack-source-absolute-path-bug
• yarn install && yarn build

see file src/index.js

const foo = Math.random() > 0.5 ? "a" : "b";
const m = require(`./foo/${foo}.js`);
console.log(m);

see file dist/main.js.map.json line 8

{
  "version": 3,
  "file": "main.js",
  "mappings": "...",
  "sources": [
    "webpack:///./src/foo/a.js",
    "webpack:///./src/foo/b.js",
    "webpack:////Users/zhaojinxiang/repos/webpack-sourcemap-bug/src/foo|sync|/^\\.\\/.*\\.js$/",
    "webpack:///webpack/bootstrap",
    "webpack:///webpack/runtime/hasOwnProperty shorthand",
    "webpack:///./src/index.js"
  ],
}

You can find a absolute file path in line 8

What is the expected behavior?

It should be

{
  "version": 3,
  "file": "main.js",
  "mappings": "...",
  "sources": [
    "webpack:///./src/foo/a.js",
    "webpack:///./src/foo/b.js",
    "webpack:///./src/foo|sync|/^\\.\\/.*\\.js$/",
    "webpack:///webpack/bootstrap",
    "webpack:///webpack/runtime/hasOwnProperty shorthand",
    "webpack:///./src/index.js"
  ],
}

Other relevant information: webpack version: 5.67.0 Node.js version: v16.12.0 Operating System: macos 12.1

[sokra]

Bug in ContextModule. It should use relative source paths for new OriginalSource, similar to NormalModule

[cool-little-fish]

yeah, and actually that’s what I am trying to do…