-
-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhance @nestia/sdk
performance by abandoning ts-node
#893
Comments
안녕하세요. 라이브러리를 잘 만들어주신 덕분에 편하게 개발하고 있습니다. 언급해주신 기능으로 개발에 필요한 몇가지를 자동화해서 사용하고 있는데 아 그리고 Nestjs로 개발할때 watch 옵션에 의해 소스 변경시 앱이 새로고침 되는데 |
@Untaek Whille Therefore, automatic swagger documents' refreshing is not possible until |
Will try |
Thank you for answer, is it possible to make the |
Current
@nestia/sdk
is usingawait import
statement for every controller classts
files withts-node
. Therefore,@nestia/sdk
is repeating TypeScript source parsing through TypeScript compiler API whenever new controller class comes, and such repeated process is making SDK library and Swagger Documents generation speed extremely slower.To reduce the generation time, I'll abandon the
await import
statement withts-node
, and inject metadata information in the compilation level through transform API. Instead, this strategy requires@nestia/core
must be required even when using only@nestia/sdk
, but I think reducing generation time would be valuable for enduring the dependency.The text was updated successfully, but these errors were encountered: