parser: module information does not include type, interface, or namespace exports

[nebrius]

This one is something of a follow-up to #10505 (comment) for some other instances where types are not listed in module outputs (sorry for not thinking to check this edge case when I filed the first bug).

import oxc from 'oxc-parser';

const code = `export type Foo = {}

export interface Bar {}

export namespace Baz {}`;

const result = oxc.parseSync('/project/a.ts', code, {
  sourceType: 'module',
});

console.log(result.module.staticExports);

Actual output:

[] // empty array

Expected output:

An array with three entries describing the three type exports.

[Boshen]

I didn't anticipate for usages of TypeScript exports so they were excluded.

[nebrius]

I didn't anticipate for usages of TypeScript exports so they were excluded.

No worries, I fully relate to the whack-a-mole nature of this kind of work. I've been doing various forms of code analysis based on TypeScript ASTs for many years, and I also still kinda regularly forget various edge cases 😃

And again, the performance of OXC compared to typescript-eslint's parser is an absolute breath of fresh air!

[magic-akari]

May I take ownership of this implementation? I'd be happy to prepare a PR once completed.

[ulrichstark]

This issue is probably also closed by #10532

Edit: Added a test for this issue to my PR

[nebrius]

I just tested this fix with a locally built copy of OXC, and it works perfectly. Thanks everyone for the fixes! Do y'all have a sense when the updated package will be published to npm?

[Boshen]

I just tested this fix with a locally built copy of OXC, and it works perfectly. Thanks everyone for the fixes! Do y'all have a sense when the updated package will be published to npm?

Released in oxc v0.67.0