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
Nest seems to be the next most popular library built on top of Exprsess. There is enough interest from one of our most important developer partners that I would like to work on enabling this library.
Here we go.
get reflect-metadata to work
Write basic example
Write tests
We shouldn't have to use the ExpressAdapter explicitly, why couldn't nest automatically use Express?
allow aliases as well from the dev side, that will help with quick testing and allow people to do their own quick patching
esbuildPluginTsc does it run on every possible file? Can we scope it somehow? What about the import type issues?
should reflect-metadata always be a part of Azle?
The nest CLI isn't going to work...how do we deal with that?
clean up dependencies and such
careful there is a weird type export issue now...where you have to put type on the import if the export is a type, I am not sure how widespread this is. I imagine this is because of the reflect-metadata stuff
Release candidate for testing
Make process.stdout/stderr print nicer
add npm_external and all dfx.json extra properties to the azle book (will cover this in dfx extensions)
Fix large files tests
update dfx
remove suspicious sections of code
put 1 gib tests back in large files
Get rid of all test code
update to type: azle in dfx.json
The text was updated successfully, but these errors were encountered:
Nest seems to be the next most popular library built on top of Exprsess. There is enough interest from one of our most important developer partners that I would like to work on enabling this library.
Here we go.
The text was updated successfully, but these errors were encountered: