Skip to content

Conversation

Bashamega
Copy link
Contributor

Split #2104

@Bashamega
Copy link
Contributor Author

I have fixed it @jakebailey :)

@jakebailey jakebailey merged commit 21e93bf into microsoft:main Aug 6, 2025
6 checks passed
@Bashamega Bashamega deleted the ts-node-res branch August 6, 2025 10:59
@jakebailey
Copy link
Member

To be clear this is fine, but I probably should have suggested just using nodenext

@Bashamega
Copy link
Contributor Author

To be clear this is fine, but I probably should have suggested just using nodenext

If you want, I can open another PR

@@ -1,5 +1,5 @@
import { parse, type Value, type Node } from "kdljs";
import type { Enum, Event, Property, Interface, WebIdl } from "./types";
import type { Enum, Event, Property, Interface, WebIdl } from "./types.js";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Too late but this should really be d.ts

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, definitely not; this is correct.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that the PR moved the file to .ts; you can't import a .d.ts file straight up like that without also enabling flags that allow importing TS files.

@@ -1,4 +1,4 @@
import * as Browser from "./types";
import * as Browser from "./types.js";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same

} from "bcd-idl-mapper";
import api from "bcd-idl-mapper";
import * as Browser from "../types";
import * as Browser from "../types.js";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same

@jakebailey
Copy link
Member

To be clear this is fine, but I probably should have suggested just using nodenext

If you want, I can open another PR

If you do I'll approve it; node16 is likely going to be deprecated in 6.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants