Spec dev vs prod environment config layer #17

New issue

Closed

opened 2026-06-25 03:11:38 +00:00 by Mark · 1 comment

Mark commented

2026-06-25 03:11:38 +00:00

Owner

service#3 added VITE_EASYSTITCH_API_URL (prod) and EASYSTITCH_API_URL (vite proxy target). Two URLs, two scopes. The build process needs:

.env.development vs .env.production split
CI/CD builds the prod bundle with the right URL baked in
Preview mode (vite preview) -- does it use the dev proxy or the prod URL?

Acceptance: ThreadCraft's build outputs (npm run build, npm run preview) talk to the correct service URL without manual env-var wrangling.

service#3 added VITE_EASYSTITCH_API_URL (prod) and EASYSTITCH_API_URL (vite proxy target). Two URLs, two scopes. The build process needs: - .env.development vs .env.production split - CI/CD builds the prod bundle with the right URL baked in - Preview mode (vite preview) -- does it use the dev proxy or the prod URL? Acceptance: ThreadCraft's build outputs (npm run build, npm run preview) talk to the correct service URL without manual env-var wrangling.

Mark added the

feature-request

needs-decompose

triage-approved

labels

2026-06-25 03:11:38 +00:00

Mark removed the

feature-request

label

2026-06-28 04:45:17 +00:00

Mark commented

2026-06-28 05:04:52 +00:00

Author

Owner

Auto-triage: needs decompose

Marked triage-approved + needs-decompose. decompose-executor will pick this up and break it into implementable sub-issues.

## Auto-triage: needs decompose Marked `triage-approved` + `needs-decompose`. decompose-executor will pick this up and break it into implementable sub-issues.

Mark

2026-06-28 05:14:22 +00:00