Generate functions-manifest.json #33667
Assignees
Comments
shuding
added this to To do
in React Server Components in Next.js (Alpha)
via automation
huozhi
moved this from To do
to In Progress
in React Server Components in Next.js (Alpha)
React Server Components in Next.js (Alpha)
automation
moved this from In Progress
to Done
Jan 31, 2022
kodiakhq bot
pushed a commit
that referenced
this issue
Jan 31, 2022
## Feature Reuse most of the part from manifest plugin to generate similar assets Resolves #33667 - [x] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [x] Related issues linked using `fixes #number` - [x] Integration tests added
natew
pushed a commit
to natew/next.js
that referenced
this issue
Feb 16, 2022
## Feature Reuse most of the part from manifest plugin to generate similar assets Resolves vercel#33667 - [x] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [x] Related issues linked using `fixes #number` - [x] Integration tests added
|
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For #31317 and other issues, we can no longer using middleware to host the SSR handler. Instead these routes should be generated as standalone functions, and we should emit a
functions-manifest.jsonfile to indicate the target function runtime and other information.The text was updated successfully, but these errors were encountered: