Fix: virtual modules excluded for babel-loader

[ndelangen]

Closes #22300

What I did

How to test

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• If this PR should be tested against many or all sandboxes,
  make sure to add the ci:merged or ci:daily GH label to it.
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

[tmeasday]

Seems like the right approach! Do we need to do similar for Vite do you think?

[ndelangen]

@tmeasday I don't know if vite suffers from the same problem, I though it didn't..
So I think, doing the same for vite isn't needed.

I was thinking that maybe there would be a need to add some sort of loader for ONLY these entries, possibly an esbuild-loader or something.

It seems though that it's not needed, considering the sandboxes are working?!

[tmeasday]

It seems though that it's not needed, considering the sandboxes are working?!

I think that's right. As I said, it's very simple handwritten JS. I guess we just need to be slightly careful we don't use any advanced JS in there, but I think by the nature of being JS (not TS) that's not likely.

@tmeasday I don't know if vite suffers from the same problem, I though it didn't..
So I think, doing the same for vite isn't needed.

I guess Vite is not going to suffer from this exact problem (the stripped comment is for webpack after all), so I guess you are right.

[ndelangen]

I marked this ready for review then.