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

[FEAT] Code splitting #8

Open
aleksasiriski opened this issue Apr 28, 2024 · 1 comment
Open

[FEAT] Code splitting #8

aleksasiriski opened this issue Apr 28, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@aleksasiriski
Copy link
Member

Every route should only have the code needed for it to run. This should be an option since it complicates deployment.

@aleksasiriski aleksasiriski added the enhancement New feature or request label Apr 28, 2024
@aleksasiriski
Copy link
Member Author

This should be optional, since it can impact performance, e.g. when a site has small number of requests and it makes sense to keep the function warm, or when the requests are expected to result in more requests (again, having the function warm is useful). Also, code splitting would only be good when the routes are large and the splitting actually makes the cold start faster, otherwise if it doesn't make the cold start any faster it's just fasting useful warm lambdas.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant