Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ESM Version of Typescript in Node Package #57010

Closed
1 task done
jogibear9988 opened this issue Jan 10, 2024 · 6 comments
Closed
1 task done

ESM Version of Typescript in Node Package #57010

jogibear9988 opened this issue Jan 10, 2024 · 6 comments
Labels
Question An issue which isn't directly actionable in code

Comments

@jogibear9988
Copy link

Acknowledgement

  • I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

Comment

Is there a plan to include a ESM Version of Typescript in the Typescript nodejs package? Or does there exist one?

@RyanCavanaugh
Copy link
Member

Not yet, and no imminent plans for one.

@RyanCavanaugh RyanCavanaugh added the Question An issue which isn't directly actionable in code label Jan 11, 2024
@jakebailey
Copy link
Member

See also #51440.

@jogibear9988
Copy link
Author

#32949

@jogibear9988
Copy link
Author

jogibear9988 commented Jan 11, 2024

Not yet, and no imminent plans for one.

sad...

currently I'm workin on a vscode HTML Designer WYSIWYG Addon for VSCode (https://marketplace.visualstudio.com/items?itemName=node-projects.vscode-designer-addon) wich uses typescrit for parseing inside a webview, wich should load esm modules via importmap (https://github.com/node-projects/vs-code-designer-addon/blob/9a776a01fd4b6c5a9bdf2a3a21cb671e7eda9edb/src/vscode/DesignerTextEditor.ts#L174) and one of the imports should use typescript (https://github.com/node-projects/web-component-designer/blob/08c50e1ccddfabbead11fa2e840931ebb7619a83/packages/web-component-designer-htmlparserservice-base-custom-webcomponent/src/service/htmlParserService/BaseCustomWebcomponentParserService.ts#L2)
But maybe I could load TS as a global instance, I'll test and will see...

@jogibear9988
Copy link
Author

I fixed it now by using a global script import, but now I have no types. For this I created another issue: #57019

@typescript-bot
Copy link
Collaborator

This issue has been marked as "Question" and has seen no recent activity. It has been automatically closed for house-keeping purposes.

@typescript-bot typescript-bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question An issue which isn't directly actionable in code
Projects
None yet
Development

No branches or pull requests

4 participants