You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Again, can be fixed by pinning vite in "resolutions". Suggested fix seems to be setting moduleResolution: bundler in tsconfig but this produces tons more issues
'correct' fix is probably upgrading yarn and using "moduleResolution": "bundler" for typescript on the client but each present a whole new set of problems to figure out
npm might be worth a try..
The text was updated successfully, but these errors were encountered:
npm is much smoother sailing, I'm happy to switch and not look back
I don't currently see a way to make moduleResolution: bundler (or es2016) work with some of our dependencies so we may need to just pin vite to v4 for now
sgfost
added a commit
to sgfost/port-of-mars
that referenced
this issue
Dec 22, 2023
occurring in #925 and whenever packages are upgraded with yarn
seems like two issues:
1. bug in yarn (classic) with resolving eslint dependencies:
Can be fixed by pinning certain versions or upgrading yarn (which comes with more problems)
2. vite 5.0 gets picked up as a dependency for vitest which contains some import that TS doesn't handle correctly
Again, can be fixed by pinning vite in
"resolutions"
. Suggested fix seems to be settingmoduleResolution: bundler
in tsconfig but this produces tons more issues'correct' fix is probably upgrading yarn and using
"moduleResolution": "bundler"
for typescript on the client but each present a whole new set of problems to figure outnpm might be worth a try..
The text was updated successfully, but these errors were encountered: