MSW does not intercept requests when the node http(s) library is imported using * as about msw

[aduth]

Another related effect of this is that MSW doesn't intercept correctly when using named ES module exports from the relevant default Node modules.

Example:

// Not intercepted:
import { get } from 'node:https';

get('https://example.com', (response) => { /* ... */ });

// Intercepted as expected:
import https from 'node:https';

https.get('https://example.com', (response) => { /* ... */ });

[kettanaito]

Hi, @mickdekkers. Thanks for reporting this!

Alas, this is a technical limitation, and to my best knowledge we cannot solve it. When you import something as a wildcard import * as X from Y, JavaScript creates a special object called Y in that module's scope. The properties of that object are readonly and their reassignment seems to be protected even on runtime.

This code throws:

import * as http from 'http'

http.get = () => {}

This code doesn't:

import http from 'http'

http.get = () => {}

The same goes for named exports mentioned by @aduth. Reassigning the named export is not possible because it's a local variable created in that module's scope upon importing. You cannot reassign those:

import { get } from 'http'

get = () => {} // Error

I don't think it's possible to support these two use cases. If it's the code you control, I recommend importing the native Node.js modules using the default export. If it's the code you don't own, neither of us can do much about it.

[kettanaito]

For the third-party code, I believe import * as http from 'http' is an incorrect way to import built-in Node.js modules. You can consider raising a pull request to that library's repo and see if they would agree on that.

[aduth]

I wonder if the new Node module loader hooks could be an option here to override how the HTTP modules are resolved?

https://nodejs.org/api/module.html#hooks

Granted:

• It may add some complexity for how hooks are registered
• May be additional overhead to manage both ESM and CommonJS
• Hooks are “release candidate” but still not fully stable