Skip to content

refactor tooling and stabilize app builds - #33

Merged
yossdotpro merged 2 commits into
yossdotpro:mainfrom
paopaonyapi-creator:main
Sep 27, 2026
Merged

yossdotpro merged 2 commits into
yossdotpro:mainfrom
paopaonyapi-creator:main

Conversation

@paopaonyapi-creator

Copy link
Copy Markdown

Align the lint and TypeScript ESLint stack with the current setup, remove the npm lockfile in favor of Yarn, and keep generated type references consistent with the Next.js dev output.

Upgrade the linting and styling toolchain, refactor the affected UI hooks and components to satisfy the new rules, and remove deprecated config and unused dependencies so the app builds and lint checks pass again.
Align the lint and TypeScript ESLint stack with the current setup, remove the npm lockfile in favor of Yarn, and keep generated type references consistent with the Next.js dev output.
@vercel

vercel Bot commented May 28, 2026

Copy link
Copy Markdown

@paopaony555 is attempting to deploy a commit to the Personal and Freelance Team on Vercel.

A member of the Team first needs to authorize it.

@yossdotpro
yossdotpro merged commit b7225db into yossdotpro:main Sep 27, 2026
1 check failed
@yossdotpro

Copy link
Copy Markdown
Owner

Hi @paopaonyapi-creator, thanks a lot for taking the time to work on this, the ESLint 9 migration was something the project needed.

Unfortunately I had to revert this PR (9fab27a). It deleted postcss.config.js and added an empty postcss.config.mjs, so Tailwind was no longer processed. The build still passed, but the production CSS shipped the raw @tailwind directive with no utility classes (≈7 KB vs ≈45 KB before), which left the site unstyled.

I've also added a Contribution Agreement to the README. It covers relicensing, because I may offer a paid desktop edition in the future. This PR was merged before that agreement existed.

If you'd like to try again, a new PR is very welcome. Just keep a valid PostCSS config (tailwindcss + autoprefixer), and by opening it you'll be accepting the terms in the README. Thanks again! 🙏

@yossdotpro yossdotpro mentioned this pull request Sep 27, 2026
3 tasks
yossdotpro pushed a commit that referenced this pull request Sep 27, 2026
Runs on pushes to main and on pull requests. The last step fails when
the built CSS still contains raw @tailwind directives, which is how the
empty PostCSS config from #33 reached production with a passing build.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017FCnaKB8E5VnYs6w8frwyf
yossdotpro pushed a commit that referenced this pull request Sep 27, 2026
Runs on pushes to main and on pull requests using Yarn through
Corepack. The last step fails when the built CSS still contains raw
@tailwind directives, which is how the empty PostCSS config from #33
reached production with a passing build.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017FCnaKB8E5VnYs6w8frwyf
pull Bot pushed a commit to A-Archives-and-Forks/removerized that referenced this pull request Sep 27, 2026
This reverts commit b7225db. yossdotpro#33 deleted postcss.config.js and added an
empty postcss.config.mjs, so Tailwind was no longer processed: the
production CSS shipped the raw @tailwind directive and no utility
classes (7 KB vs 45 KB before), leaving the site unstyled.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017FCnaKB8E5VnYs6w8frwyf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants