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
I'm developing with Nest.js v11 and tested SWC for faster builds.
Jest Tests: 71s → 20s
nest start -b swc: 7.69s → 2.16s
nest start -b swc --type-check: 8s (same as old tsc build)
Since enabling type checking doesn't provide much of a speed improvement, fully adopting SWC for my workflow is challenging.
Current Workaround:
I’m using SWC only for Jest tests to speed up development.
For deployments, I’m still using the standard tsc build for type checking.
Additionally, since the speed difference in local development is minimal, I continue using tsc for builds.
Question:
Is there a way to improve SWC's type-checking speed?
Can it be optimized or parallelized for better performance?
Thanks!
Babel plugin or link to the feature description
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the feature
I'm developing with Nest.js v11 and tested SWC for faster builds.
Since enabling type checking doesn't provide much of a speed improvement, fully adopting SWC for my workflow is challenging.
Current Workaround:
I’m using SWC only for Jest tests to speed up development.
For deployments, I’m still using the standard tsc build for type checking.
Additionally, since the speed difference in local development is minimal, I continue using tsc for builds.
Question:
Is there a way to improve SWC's type-checking speed?
Can it be optimized or parallelized for better performance?
Thanks!
Babel plugin or link to the feature description
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: