I'm working at StackBlitz and I was going through some of the starters. There I noticed that the NestJS starter was broken. The reason is that we automatically load @swc/wasm if we detect the usage of @swc/core. They are released in sync which means the versions between both (should) match.
The version in the package-lock.json was @swc/core@1.3.67, which never got released in @swc/wasm for whatever reason.
By reinstalling the dependencies, it bumps the version to a higher one which does exist.
kamilmysliwiec
commented
1 year ago
Hey 👋
I'm working at StackBlitz and I was going through some of the starters. There I noticed that the NestJS starter was broken. The reason is that we automatically load
@swc/wasmif we detect the usage of@swc/core. They are released in sync which means the versions between both (should) match.The version in the
package-lock.jsonwas@swc/core@1.3.67, which never got released in@swc/wasmfor whatever reason.By reinstalling the dependencies, it bumps the version to a higher one which does exist.