Enhance Tailwind config with custom themes #277
Conversation
Added custom theme extensions and dark mode support.
|
@chi20253032 is attempting to deploy a commit to the Toa Kiryu's Collective Team on Vercel. A member of the Team first needs to authorize it. |
This workflow installs Node.js dependencies, builds the source code, and runs tests across multiple Node.js versions.
There was a problem hiding this comment.
Pull Request Overview
This pull request enhances the Tailwind CSS configuration and adds a CI/CD workflow for automated builds and tests.
- Extended Tailwind configuration with custom breakpoints, fonts, shadows, and comprehensive theming
- Added GitHub Actions workflow for Node.js CI across multiple Node versions
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| tailwind.config.ts | Extended Tailwind theme with additional breakpoints (3xl, 4xl), custom font families (Inter, Poppins), enhanced border radius options, and custom box shadows for improved design flexibility |
| .github/workflows/node.js.yml | Added new CI workflow to run builds and tests on Node.js 18.x, 20.x, and 22.x for all pushes and pull requests to the main branch |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| cache: 'npm' | ||
| - run: npm ci | ||
| - run: npm run build --if-present | ||
| - run: npm test |
There was a problem hiding this comment.
The GitHub Actions workflow will fail because there is no test script defined in package.json. The workflow runs npm test (line 31), but package.json only defines dev, build, postbuild, start, and lint scripts. Either add a test script to package.json or remove the npm test line from the workflow.
| - run: npm test |
1 participant
Added custom theme extensions and dark mode support.
Why:
Closes:
What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following:
I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).
datadirectory.For content changes, I have completed the self-review checklist.