I’ve tried this across multiple projects, including blank Node.js projects created with npm init and tsc init, and on both VSCode (Mac) and Emacs (Linux), using LSP in both cases --- to rule out client-side issues. That makes me doubt it’s just a configuration problem. Still, if you think it might be, I’d gladly take a working configuration to compare against.

For now, I’ve accepted one explanation I found on Stack Overflow: the language server just don't support CommonJS’ dynamic exports. That said, if anyone has a more optimistic answer, I’d love to hear it.

You haven't mentioned "dynamic" exports before. Normal CommonJS exports should work fine.

Again, it would help to see specific repo example and stating what you expect to work exactly but at least chatgpt thinks that typescript can have problems with some types of Commonjs exports.

Here’s a demo. All CommonJS exports (https://nodejs.org/api/modules.html) are dynamic; they happen by mutating module.exports at runtime. I don't know what a "normal" CommonJS exports is, are you referring to ECMAScript exports (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/export)?

I believe it works if you rename the files to use the *.js extension (and remove type annotations and possibly add checkJs: true in tsconfig.json).

I don't know if that's expected behavior but that would be a question to the typescript repo.