No sourcemaps for Selenium/headless chrome client tests?

[drone1]

Hi, I could really use some assistance to get sourcemaps working for client-side callstacks in headless chrome.

My command looks something like this:

> TEST_BROWSER_DRIVER=chrome TEST_CHROME_ARGS='start-maximized enable-automation --headless --no-sandbox --disable-dev-shm-usage --disable-browser-side-navigation --disable-gpu --ignore-certificate-errors' TEST_CLIENT=1 TEST_SERVER=1 ROOT_URL=https://www.dev-test.com:3000 SERVER_NODE_OPTIONS='--trace-uncaught --trace-warnings' meteor test --port 3006 --extra-packages xolvio:cleaner meteortesting:mocha@3.2.0 meteortesting:browser-tests@1.7.0 meteortesting:mocha-core@8.2.0 --driver-package meteortesting:mocha --full-app --settings test.json

(3000 is the SSL port and 3006 is for HTTP; requests are proxied and work fine)

Anything obviously missing here? Am I barking up the right tree?

Thanks.

[github-actions]

Thank you for submitting this issue!

We, the Members of Meteor Community Packages take every issue seriously.
Our goal is to provide long-term lifecycles for packages and keep up
with the newest changes in Meteor and the overall NodeJs/JavaScript ecosystem.

However, we contribute to these packages mostly in our free time.
Therefore, we can't guarantee you issues to be solved within certain time.

If you think this issue is trivial to solve, don't hesitate to submit
a pull request, too! We will accompany you in the process with reviews and hints
on how to get development set up.

Please also consider sponsoring the maintainers of the package.
If you don't know who is currently maintaining this package, just leave a comment
and we'll let you know

[drone1]

It would so appreciated if any guidance could be provided here.

Not having sourcemaps load for client tests makes TDD tedious and expensive. Is this supposed to work out of the box? Is there some more information I can provide, or is there anything I can do to load sourcemaps for client-side headless chrome tests? Thank you.