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
[ ] Regression
[ X] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.
I am not sure if this is a bug, or a feature request.
Current behavior
git clone https://github.com/TrilonIO/nestjs-azure-functions - the azure func demo app.
npm install --save @nestjs/platform-fastify
npm install the rest.
Swap the default express adaptor with the fastify one.
Make sure you have Azure's func cli installed, then npm run build && func host start.
Open a valid endpoint. In this case, the url logged when func host start has completed and the server is running.
Expected behavior
Fastify should have the same 200 success response as Express adaptor.
Minimal reproduction of the problem with instructions
See instructions above.
What is the motivation / use case for changing the behavior?
I'd like to use Fastify with Azure functions as it's lighter weight and faster.
I'm submitting a...
I am not sure if this is a bug, or a feature request.
Current behavior
git clone https://github.com/TrilonIO/nestjs-azure-functions
- the azure func demo app.npm install --save @nestjs/platform-fastify
npm install
the rest.npm run build && func host start
.func host start
has completed and the server is running.Expected behavior
Fastify should have the same 200 success response as Express adaptor.
Minimal reproduction of the problem with instructions
See instructions above.
What is the motivation / use case for changing the behavior?
I'd like to use Fastify with Azure functions as it's lighter weight and faster.
Environment
MacOS Catalina
NodeJS: 12.16.3
NestJS common, core: 7.0.8
NestJS platform-fastify 7.0.11
@nestjs/azure-func-http: 0.5.0
@azure/functions: 1.0.3
Others:
npm
VSCode
zsh
The text was updated successfully, but these errors were encountered: