Ensure build-time tooling is available for RSS and Tailwind CSS#137
Ensure build-time tooling is available for RSS and Tailwind CSS#137Copilot wants to merge 5 commits intoclaude/refactor-website-spa-17k23from
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-authored-by: alexwelcing <13339261+alexwelcing@users.noreply.github.com>
Co-authored-by: alexwelcing <13339261+alexwelcing@users.noreply.github.com>
|
00:24:00.476 Running build in Washington, D.C., USA (East) – iad1 @copilot Please fix |
Co-authored-by: alexwelcing <13339261+alexwelcing@users.noreply.github.com>
Co-authored-by: alexwelcing <13339261+alexwelcing@users.noreply.github.com>
Moved Tailwind/PostCSS (including nesting plugin) into production dependencies and pinned the lockfile to known compatible versions so the build can resolve tailwindcss/nesting. Commit: 5bd0259. |
|
@copilot okay, cool. I think you need to do a push to determine if this works in vercel? |
The latest fixes are already pushed to the branch (most recent commit 5bd0259). Vercel should pick up the new commit automatically; if it hasn’t, triggering a redeploy from Vercel will re-run the build with the updated dependencies. |
Vercel builds failed because build-time tooling was missing during the production install, preventing both RSS generation and Tailwind CSS nesting from resolving before
next build.tsxand Tailwind/PostCSS build tooling (tailwindcss,postcss,postcss-nesting,autoprefixer,@tailwindcss/typography) fromdevDependenciestodependenciesso build-time scripts and CSS processing can resolve in production installs.Example:
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.