Open ryanfchase opened 1 month ago
git checkout main
git pull
rm -rf node_modules
npm install
.env
with VITE prefixnpm run setup
npm start
http://localhost:5173/
git checkout main
git pull
rm -rf node_modules
npm install
npm run setup
npm start
http://localhost:5173/
git checkout main
git pull
rm -rf node_modules
npm install
npm run setup
npm start
http://localhost:5173/
git checkout main
git pull
rm -rf node_modules
npm install
npm run setup
npm start
http://localhost:5173/
git checkout main
git pull
rm -rf node_modules
npm install
npm run setup
npm start
http://localhost:5173/
git checkout main
git pull
rm -rf node_modules
npm install
npm run setup
npm start
http://localhost:5173/
git checkout main
git pull
rm -rf node_modules
npm install
npm run setup
npm start
http://localhost:5173/
git checkout main
git pull
rm -rf node_modules
npm install
npm run setup
npm start
http://localhost:5173/
git checkout main
git pull
rm -rf node_modules
npm install
npm run setup
npm start
http://localhost:5173/
git checkout main
git pull
rm -rf node_modules
npm install
npm run setup
npm start
http://localhost:5173/
Hi @ryanfchase, what's the purpose of the Action Items: GH Pages from Fork checklist? I'm not clear on why each dev needs to deploy their own fork to GitHub Pages.
That second checklist seems like a lot of extra work, given that we can all continue to develop as normal (without forking) once #1822 has been merged into main.
Hi @ryanfchase, what's the purpose of the Action Items: GH Pages from Fork checklist? I'm not clear on why each dev needs to deploy their own fork to GitHub Pages.
That second checklist seems like a lot of extra work, given that we can all continue to develop as normal (without forking) once #1822 has been merged into main.
Hey @aqandrew -- it's not required. I figured I'd list the steps in case anyone else wanted to try it out. I've left it there so I can document it in a wiki page later. I'll update the ticket to note that it's optional. 😄
Overview
We need to track each dev that is currently active and ensure that they have migrated to Vite in order to avoid merge conflicts or other issues.
Action Items
Create comments for each dev, use template to track their progress
Resources
Instructions for Vite Environment Variables
All environment variables must have a prefix of VITE. Two tokens are most relevant for your dev environment:
MAPBOX_TOKEN
becomesVITE_MAPBOX_TOKEN
CONTENTFUL_SPACE
becomesVITE_CONTENTFUL_SPACE
Action Item Templates For Devs
Mandatory for each dev, everyone's tracking comment includes these steps.
Optional Steps for Dev
Only follow these steps if you need to be able to publish your fork via gh pages.