This repository has been archived by the owner on Jan 28, 2025. It is now read-only.
Autogenerate Serverless Config #418
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…danielcondemarin/serverless-next.js into auto-generate-serverless-config
sclaughl
pushed a commit
to sclaughl/serverless-next.js
that referenced
this pull request
Jul 16, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently it is required that users specify "serverless" target in their config or "experimental-serverless-trace".
This PR makes serverless-next.js autogenerate the config. by creating a temporary
next.config.jsoverriding the target specified with "serverless" or "experimental-serverless-trace". This will allow in future to transparently swap out which target is used behind the scenes without users even noticing.To opt-in for "experimental-serverless-trace" simply: