Next.js Support
Open
Nobody has claimed this yet.
✨ enhancement
📚 libraries
- Dominant language
- TypeScript
- Stars
- 5.4k
- Forks
- 215
- Avg merge
- 2h 9m
- Merged PRs (30d)
- 27
Description
Use Case
https://nextjs.org/ is a massively popular framework, so it would be great to have good support for deploying a wing application with it.
Proposed Solution
@winglibs/nextjs
Implementation Notes
Unlike our current Website and React abstractions, nextjs is not just a static site generator.
Maybe need https://github.com/sst/open-next
Component
No response
Community Notes
- Please vote by adding a 👍 reaction to the issue to help us prioritize.
- If you are interested to work on this issue, please leave a comment.
- If this issue is labeled needs-discussion, it means the spec has not been finalized yet. Please reach out on the #dev channel in the Wing Discord.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing Website and React abstractions, then examine the proposed @winglibs/nextjs package and SST's open-next project. The issue needs a defined deployment design for Next.js beyond static sites; done should mean an agreed specification and working support for deploying a Wing application with Next.js.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- next.js
- Domain
- cloud, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100