After the issues earlier today with @swc/core in #11609, we now are starting to see similar problems on Windows agents. The underlying issue is that the version of ts-node we depend on has a peer dependency on @swc/core with a version ">=1.2.50", and @swc/core seems to have very rapid pushes to public which are inadequately tested.
After the issues earlier today with @swc/core in #11609, we now are starting to see similar problems on Windows agents. The underlying issue is that the version of ts-node we depend on has a peer dependency on @swc/core with a version ">=1.2.50", and @swc/core seems to have very rapid pushes to public which are inadequately tested.
https://build.palaso.org/buildConfiguration/Keyman_Common_KPAPI_TestPullRequests_Windows/467276?buildTab=log&linesState=98&logView=flowAware
We may be able to update ts-node in our local package.json? Will test this.