https://github.com/zephraph/next-now-ssr-issue
https://github.com/zephraph/next-now-ssr-issue
Last synced: about 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/zephraph/next-now-ssr-issue
- Owner: zephraph
- Created: 2020-04-29T21:31:01.000Z (almost 5 years ago)
- Default Branch: master
- Last Pushed: 2020-07-23T03:53:26.000Z (almost 5 years ago)
- Last Synced: 2025-01-04T07:25:38.382Z (4 months ago)
- Language: JavaScript
- Homepage:
- Size: 1.64 MB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Next Now SSR Bug reproduction
**Note**: This is fixed when tested on vercel 19.2.0. Everything below is out of date and for historical context.
---
This is a simple static + next.js app that specify's a custom now build and routing.
```
{
"version": 2,
"build": {
"env": {
"BUILDING_FOR_NOW": "true"
}
},
"builds": [
{ "src": "index.html", "use": "@now/static" },
{ "src": "apps/package.json", "use": "@now/next" }
],
"routes": [{ "src": "/next(.*)", "dest": "apps/$1" }]
}
```
**What I expect**
Navigating to `/next/123` should render the `[post]` page and output `Your post id is 123`.
**What's Happening**
`/next/123` produces a 404. `/apps/123` renders the page, but doesn't pass down the SSR response.