![]() ![]() I'd be really interested to help exploring more possibilities to use swc with nest :) Rewrite the plugins to use the swc AST?.Add a transfomer for swc tsc AST compat?.Rewrite the plugins as swc plugins (I think that's the way nextjs does it with their plugins for styled-components and relay). ![]() There would be several ways to solve this: swagger, graphql) that rely on manipulating the AST emitted by tsc (which is not compatible with the AST from swc out of the box). There were some great answers in the previous thread (originally about esbuild) here:Īs mentioned by there are several plugins (e.g. I haven't tested support in monorepos, though. I experimented with a repository already (dev server, build and running jest tests via swc) which could maybe a starting point for experimenting with swc: What is the motivation / use case for changing the behavior? Still, I think it's useful to have an issue dedicated specifically for SWC rather than hijacking a closed one about esbuild. I understand a lot of the work that needs to be done is not necessarily on Nest's side, but rather on SWC's side to fix it's issues. CLI plugins that require AST transformations, certain decorators, etc. The discussion in #731 is making it evident that we are much closer to being able to have SWC build NestJS projects - the boilerplate NestJS app already runs fine from SWC builds, there are just some kinks/edge cases that need to be tracked i.e. Teachability, documentation, adoption, migration strategy ![]() Describe the solution you'd likeĪllow nest build to use swc via some flag e.g. Related to #731 in the sense that this is a request/discussion for a faster build system support, but as ESBuild are not going to support emitDecoratorMetadata anytime soon but SWC already does, I think it makes more sense to push for that. swc on the other hand takes 0.38 seconds - that's over a 10x improvement. Is your feature request related to a problem? Please describe itīuild times for large projects can be quite slow, which makes both local development and CI deploy times slow.įor a small project of mine (around 6k lines), tsc takes 5.2 seconds to build. Is there an existing issue that is already proposing this? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |