Skip to content

[Playground] Allow to set moduleResolution #174

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

Closed
danielkcz opened this issue Jan 9, 2020 · 3 comments
Closed

[Playground] Allow to set moduleResolution #174

danielkcz opened this issue Jan 9, 2020 · 3 comments

Comments

@danielkcz
Copy link

The moduleResolution is set to classic by default if ES2015+ is being targetted. Most of the code using modules expect node resolution.

Trying to reproduce the issue that depends on imports causes a different outcome, basically acts like importing untyped code.

So it's either about allowing to set this configuration or better way as suggested by @DanielRosenwasser at microsoft/TypeScript#35876 (comment) to assume that most people will use node.

Related #21, microsoft/TypeScript#11434

@orta
Copy link
Contributor

orta commented Jan 12, 2020

Good points! This will be in the v2 playground now with a0dee66 on the next v2 deploy when #176 is merged (if you want to try porting it to the current playground change this file)

@orta
Copy link
Contributor

orta commented Feb 14, 2020

This is in
Screen Shot 2020-02-14 at 9 09 44 AM

@orta orta closed this as completed Feb 14, 2020
@tjx666
Copy link

tjx666 commented Apr 12, 2023

@orta module option is not equals to moduleResolution

I can use module: ESNext, but moduleResolution: nodenext:

image

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

No branches or pull requests

3 participants