- Front end dev .env

Question

shyam · Accepted Answer

- Front end dev .env
  - `SENTRY_DSN="https://a154ed6452f04e0898156e1086eb1449@o4504746642178048.ingest.sentry.io/4504747535958016"`
- Back end dev .env
  - `SENTRY_DSN="https://f8757b6620b34c46973527795f72b4c5@o4504746642178048.ingest.sentry.io/4504746648338432"`
- These are now configured to go to [dev@factiii.com](mailto:dev@factiii.com "‌"), sentry charges for having multiple users, but you can have an unlimited amount of projects so we will run everything to [dev@factiii.com](mailto:dev@factiii.com "‌") and have a Front/back end dev and Front/back end production
- npm run build gets an error because there is no auth token I generated one and it did not fix it. Ideally we shouldn’t have random builds generating branches too so can you configure something like `dryRun: process.env.VERCEL_ENV !== "production"` in the configs and then have a .env variable `SENTRY_AUTH_TOKEN` ? See link below

‌

[Sentry reported an error: Authentication credentials were not provided. (http status: 401) · Discussion #583 · vercel/community (github.com)](https://github.com/vercel/community/discussions/583 "‌")

npm run build fails front end due to missing sentry credentials. See inside for more details

Activity