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

Use a modern moduleResolution strategy #4275

Closed
birkskyum opened this issue Jun 15, 2024 · 0 comments · Fixed by #4533
Closed

Use a modern moduleResolution strategy #4275

birkskyum opened this issue Jun 15, 2024 · 0 comments · Fixed by #4533

Comments

@birkskyum
Copy link
Member

birkskyum commented Jun 15, 2024

Currently, the tsconfig is set to use moduleResolution: "Node", which is deprecated:

Screenshot 2024-06-15 at 11 59 21

Going to a modern module resolution such as NodeNext (or Bundler) would likely allow us to update dependencies like:

And be a step towards

In practice "NodeNext" is more strict than what we do now, and would demand us to add file extensions (.ts/.js) on relative imports.

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