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

fix: types not read when moduleResolution is not "node" #302

Merged
merged 1 commit into from
Jul 11, 2023

Conversation

voliva
Copy link
Collaborator

@voliva voliva commented Jul 11, 2023

Fixes #298

I've brought it to @rx-state/core as well, released for 0.1.3

Sorry it took long to fix this @bmcbarron, I've tried it in local and it looks like this should work, right?

@voliva voliva requested a review from josepot July 11, 2023 14:06
@codecov
Copy link

codecov bot commented Jul 11, 2023

Codecov Report

Merging #302 (cd93c3a) into main (155fb04) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #302   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           24        24           
  Lines          390       390           
  Branches        54        54           
=========================================
  Hits           390       390           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@voliva voliva merged commit 6aa83dd into main Jul 11, 2023
4 checks passed
@voliva voliva deleted the module-resolution-fix branch July 11, 2023 19:20
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

Successfully merging this pull request may close these issues.

TypeScript moduleResolution: NodeNext expects core.es2017.d.ts types file
2 participants