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.

Sign up for GitHub

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

Jump to bottom

Confusion regarding moduleResolution: NodeNext requirement #149

Open
freshgum-bubbles opened this issue Dec 16, 2023 · 0 comments
Open

Confusion regarding moduleResolution: NodeNext requirement #149

freshgum-bubbles opened this issue Dec 16, 2023 · 0 comments
Assignees
@freshgum-bubbles
Labels
documentation Improvements or additions to documentation
Milestone
Version 1

Comments

@freshgum-bubbles
Copy link
Owner

Related to #145 (comment).

Essentially, as the package currently stands, you must use NodeNext for moduleResolution
in your tsconfig.json to import it -- this isn't a very good place to be; I'd prefer to provide support
for many more module resolution patterns, e.g. bundler.
@freshgum-bubbles freshgum-bubbles added bug Something isn't working documentation Improvements or additions to documentation labels Dec 16, 2023
@freshgum-bubbles freshgum-bubbles self-assigned this Dec 16, 2023
@freshgum-bubbles freshgum-bubbles removed the bug Something isn't working label Dec 16, 2023
@freshgum-bubbles freshgum-bubbles added this to the Version 1 milestone Dec 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@freshgum-bubbles freshgum-bubbles

Labels
documentation Improvements or additions to documentation
Projects
None yet
Milestone
Version 1
Development

No branches or pull requests
1 participant
@freshgum-bubbles