-
Notifications
You must be signed in to change notification settings - Fork 36
set up next.js app and static build #157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
📦 Build Artifacts Available |
My main open question for this PR is should we already include base github workflows that ensure the basics work. I'll probably just add those in the next PR |
I suppose at the least the failing workflows will need updating |
📦 Build Artifacts Available |
📦 Build Artifacts Available |
📦 Build Artifacts Available |
📦 Build Artifacts Available |
📦 Build Artifacts Available |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good but needs linting fixes
This is a starter next.js app set up for static builds (static site generation comes from output: 'export' in the next.config.ts). It uses the 'use client' directive to tell Next.js to treat everything as client side code in the page.tsx file meaning that most of the app won't be prerendered. This mirrors our set up since we use MUI theming and CSS in JS which require most of the app to be client code.