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
{{ message }}
This repository has been archived by the owner on Jan 28, 2025. It is now read-only.
This is great news for local development when using this plugin. Currently, when you have custom page routes you can't develop / test this locally, or at least properly, since the current serverless offline support is too limited. With dynamic routes support the users should be able to just run next dev and benefit from the development experience next provides, then is the plugin's job to provide feature parity when deploying onto AWS Lambda.
Really interested in this. Especially if it increases DX by allowing to test our code locally the same way it runs against AWS. Env reproduction is a tough part, there are many implementations of aws lambda + next out there, but very few that have a good-enough DX for a production use case.
Is there a timeline on adding this support? I've been using next.js 9.0 with this plugin and all has been well, until I needed to add a dynamic route.
I'd be happy to fork and add this in if someone could give me an idea of where to look in the codebase. I'd like to get this implemented as quickly as possible.
Motivation
Nextjs 9 introduced Dynamic Route segments as per this RFC.
What does this mean for this serverless plugin?
This is great news for local development when using this plugin. Currently, when you have custom page routes you can't develop / test this locally, or at least properly, since the current serverless offline support is too limited. With dynamic routes support the users should be able to just run
next dev
and benefit from the development experience next provides, then is the plugin's job to provide feature parity when deploying onto AWS Lambda.Proposal
Given the following app:
The plugin will automatically produce the following serverless page functions:
The option to provide custom page routes will be kept, but it is recommended you use next dynamic routes whenever possible instead.
The text was updated successfully, but these errors were encountered: