212a1cb941
* WIP: init cli + init env utils * remove pnpm global link artifacts * WIP: migrate legacy new cli command * change enums to objects * remove chromedriver package from integration test * create cli bin file that requires blitz/dist/index.cj * fix prisma-utils pEvent * fix missing modules * use form key types & rename bin script * init cli-codegen * add fs-extra package to blitz-next * read config file as a buffer then eval the string Co-authored-by: Dillon Raphael <dillonraphael@Dillons-MBP.hitronhub.home>
Getting Started
First, run the development server:
yarn dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying pages/index.js. The page auto-updates as you edit the file.
API routes can be accessed on http://localhost:3000/api/hello. This endpoint can be edited in pages/api/hello.js.
The pages/api directory is mapped to /api/*. Files in this directory are treated as API routes instead of React pages.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.