Skip to content
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

Allow statically build the API server #135

Closed
4 tasks done
nfroidure opened this issue May 26, 2022 · 0 comments · Fixed by #163
Closed
4 tasks done

Allow statically build the API server #135

nfroidure opened this issue May 26, 2022 · 0 comments · Fixed by #163
Assignees
Milestone

Comments

@nfroidure
Copy link
Owner

nfroidure commented May 26, 2022

Currently, the server uses the DI loaders to run but we could build it like we do for the GCP Functions/AWS Lambda builds.

That said, this is a huge work, so this issue will gather all the necessary work/design to achieve it.

Testing:

cd packages/whook-example;
npm run build;
# Currently not working
node dist/start.js 

Still a few things to do:

@nfroidure nfroidure self-assigned this May 26, 2022
nfroidure added a commit that referenced this issue May 26, 2022
Currently, building the whole API just means to compile the TypeScript files into JavaScript one. This allows to go further and to statically build the dependency tree like done in AWS Lambda/GPC Functions builds.

concerns #135
nfroidure added a commit that referenced this issue May 26, 2022
Currently, building the whole API just means to compile the TypeScript files into JavaScript one. This allows to go further and to statically build the dependency tree like done in AWS Lambda/GPC Functions builds.

concerns #135
@nfroidure nfroidure added this to the 13.0.0 milestone Aug 15, 2023
nfroidure added a commit that referenced this issue Aug 20, 2023
Finalizing the build of the server needed a new major version
 of Knifecycle. It now works as expected 💪.

fix #135
nfroidure added a commit that referenced this issue Aug 20, 2023
Finalizing the build of the server needed a new major version
 of Knifecycle. It now works as expected 💪.

fix #135
nfroidure added a commit that referenced this issue Aug 20, 2023
Finalizing the build of the server needed a new major version
 of Knifecycle. It now works as expected 💪.

fix #135
nfroidure added a commit that referenced this issue Aug 20, 2023
Finalizing the build of the server needed a new major version
 of Knifecycle. It now works as expected 💪.

fix #135
nfroidure added a commit that referenced this issue Aug 20, 2023
Finalizing the build of the server needed a new major version
 of Knifecycle. It now works as expected 💪.

fix #135
nfroidure added a commit that referenced this issue Aug 20, 2023
Finalizing the build of the server needed a new major version
 of Knifecycle. It now works as expected 💪.

fix #135
nfroidure added a commit that referenced this issue Aug 20, 2023
Finalizing the build of the server needed a new major version
 of Knifecycle. It now works as expected 💪.

fix #135
nfroidure added a commit that referenced this issue Aug 20, 2023
Finalizing the build of the server needed a new major version
 of Knifecycle. It now works as expected 💪.

fix #135
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant