Prevent Webpack from resolving import.meta.url statements during building (issue 19145)

[Snuffleupagus]

This fixes a Node.js-specific regression from PR #18959.

[Snuffleupagus]

/botio test

[moz-tools-bot]

From: Bot.io (Windows)

---

Received

Command cmd_test from @Snuffleupagus received. Current queue size: 0

Live output at: http://54.193.163.58:8877/20fb2845cc9c7d2/output.txt

[moz-tools-bot]

From: Bot.io (Linux m4)

---

Received

Command cmd_test from @Snuffleupagus received. Current queue size: 0

Live output at: http://54.241.84.105:8877/eeb6776be78ed99/output.txt

[moz-tools-bot]

From: Bot.io (Linux m4)

---

Failed

Full output at http://54.241.84.105:8877/eeb6776be78ed99/output.txt

Total script time: 27.71 mins

• Unit tests: Passed
• Integration Tests: Passed
• Regression tests: FAILED

  different ref/snapshot: 1

Image differences available at: http://54.241.84.105:8877/eeb6776be78ed99/reftest-analyzer.html#web=eq.log

[moz-tools-bot]

From: Bot.io (Windows)

---

Failed

Full output at http://54.193.163.58:8877/20fb2845cc9c7d2/output.txt

Total script time: 48.07 mins

• Unit tests: Passed
• Integration Tests: FAILED
• Regression tests: Passed

[nicolo-ribaudo]

Verified locally that this produces working builds.

[Snuffleupagus]

Without this patch PDF.js is basically unusable in Node.js, which means that the regression is bad enough that for once I do think that we should consider an immediate follow-up release to address this.

@timvandermeij What's your opinion on this?

[timvandermeij]

Thank you for the fix!

What's your opinion on this?

I agree with this. I'll make a new release in a bit.