https://github.com/gadingnst/nextjs13-custom-server-bug
All environment variables become `undefined` while using custom server (only on development) after upgrade to NextJS 13.
https://github.com/gadingnst/nextjs13-custom-server-bug
Last synced: 10 months ago
JSON representation
All environment variables become `undefined` while using custom server (only on development) after upgrade to NextJS 13.
- Host: GitHub
- URL: https://github.com/gadingnst/nextjs13-custom-server-bug
- Owner: gadingnst
- Created: 2022-11-11T08:43:40.000Z (about 3 years ago)
- Default Branch: main
- Last Pushed: 2022-11-11T08:56:50.000Z (about 3 years ago)
- Last Synced: 2024-10-06T06:20:14.538Z (over 1 year ago)
- Language: TypeScript
- Homepage:
- Size: 210 KB
- Stars: 0
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Passport Frontend
This is a [Next.js](https://nextjs.org/) project bootstrapped with [`create-next-app`](https://github.com/vercel/next.js/tree/canary/packages/create-next-app).
## Description
Bug: All environment variables become `undefined` while using custom server only on development after upgrade to NextJS 13.
Expected: Environment Variables doesn't `undefined`.
Note: It still works when you downgrade to `NextJS 12.3.1`
https://github.com/vercel/next.js/issues/42778