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
Setup correct target
/module
/moduleResolution
settings for TSConfig
#36
Conversation
This change doesn't provide a usable ESM module. |
5a82a66
to
f600f2d
Compare
target
/module
/moduleResolution
settings for TSConfig
Hmm, seems to work for me locally when linked into a consumer package... 🤔 |
Have you tried linking this to a typescript consumer package? |
f600f2d
to
ae1a4eb
Compare
Yep! The same one that you shared a screenshot from in #35. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for checking!
27c131e
to
e68ab4b
Compare
This partially reverts changes in c019ff4.
- Update vite + vitest to latest - use `defineConfig` from `vitest/config` instead of `vite`
This can be removed once `vitest` moves back to using `"type": "module"`
082adc5
to
70869ff
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Let's add an issue for closing the two hacks when we can, to wit:
- remove the vitest patch
- remove the private import from msw
Created #42 to track fixing those issues. |
This reverts some of the changes from #35
target
/module
/moduleResolution
settings for TSConfigmsw/lib/node/index.js
inpackages/network/__test__/fetch-test.js
in order to get TypeScript to properly typecheck themsw
patch-package
infrastructurevitest
so that we can work around issues with type resolution withinvite
(fix!: use type module (revert #1411) vitest-dev/vitest#1465)