-
Notifications
You must be signed in to change notification settings - Fork 0
Bootstrapping a new Vercel project
Initialize a new node project:
npm init
Install minimal modules we need for our project:
npm i -D next react react-dom typescript @types/react @types/react-dom @types/node sass
npm i -D @typescript-eslint/eslint-plugin @typescript-eslint/parser @typescript-eslint/typescript-estree eslint eslint-config-prettier eslint-plugin-prettier eslint-plugin-react prettier
After installing eslint, prettier and all the necessary plugins we should add the configuration for eslint.
Run following in the root of your project folder: vc
And you'll get following wizard prompts:
$ Set up and deploy “~/Documents/fdmg-projects/bnr-brandstories/bnr-branded”? [Y/n]
$ Which scope do you want to deploy to? BNR Nieuwsradio
$ Link to existing project? [y/N]
$ What’s your project’s name? bnr-branded
$ In which directory is your code located? ./
Auto-detected Project Settings (Next.js):
- Build Command: `npm run build` or `next build`
- Output Directory: Next.js default
- Development Command: next dev --port $PORT
$ Want to override the settings? [y/N]
Terminal output:
🔗 Linked to bnr/bnr-branded (created .vercel and added it to .gitignore)
🔍 Inspect: https://vercel.com/bnr/bnr-branded/HeWvVB1xFwza1bngutKcFY7Lofux [964ms]
✅ Production: https://bnr-branded.vercel.app [copied to clipboard] [44s]
📝 Deployed to production. Run `vercel --prod` to overwrite later (https://vercel.link/2F).
💡 To change the domain or build command, go to https://vercel.com/bnr/bnr-branded/settings
Run the following command to pull the environment variables set for the project in the Vercel Dashboard.
vc env pull