Skip to content

feat(seo,compare): add /compare/cursor page#48

Merged
stevenfackley merged 1 commit into
mainfrom
seo/compare-cursor
Apr 21, 2026
Merged

feat(seo,compare): add /compare/cursor page#48
stevenfackley merged 1 commit into
mainfrom
seo/compare-cursor

Conversation

@stevenfackley

Copy link
Copy Markdown
Owner

Summary

  • Fourth entry in the /compare series: /compare/cursor.
  • Honest framing: Cursor is the best AI-native IDE; the two are complementary, not competitive. Workflow positioned as "use StackAlchemist once to create the repo, then Cursor forever after."
  • Updates /compare index teaser — Cursor shipped, Replit Agent still queued.

Test plan

  • npm run lint clean
  • npx next build/compare/cursor pre-renders statically
  • CI green on PR

🤖 Generated with Claude Code

Fourth entry in the /compare series. Cursor sits in a different category
from v0/Bolt/Lovable — it is an AI-native IDE, not a prompt-to-app
generator. The honest answer is that the two are complementary, not
competitive: use StackAlchemist once to create the repo, then Cursor
forever after.

- content/compare/cursor.md: founder-voice comparison. Clear that Cursor
  is the best AI IDE, and that StackAlchemist does not compete with it
  once a repo exists. Positions the natural "use both" workflow.
- manifest: cursor entry with wins/verdict.
- /compare index: teaser now "Next up: Replit Agent".

Batch D 2/3.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@stevenfackley
stevenfackley merged commit 1926965 into main Apr 21, 2026
9 checks passed
stevenfackley added a commit that referenced this pull request Apr 21, 2026
* feat(seo,compare): add /compare/replit-agent page

Fifth and final entry in batch D of the /compare series. Replit Agent
is the closest to StackAlchemist by *promise* on the "hosted vs owned"
axis — the honest cut is runtime and ownership.

- content/compare/replit-agent.md: founder-voice comparison. Clear on
  where Replit wins (hosted runtime, flexible stack, zero infra) vs.
  where StackAlchemist wins (owned repo on your GitHub, one-time price,
  production stack done well, compile gate).
- manifest: replit-agent entry with wins/verdict.
- /compare index: teaser now "Have a tool you want us to cover?"
  Remaining SEO plan /compare entries (Bubble, Retool) are low-priority
  low-code tools — deferred.

Batch D 3/3 — /compare is now feature-complete per the SEO plan.
Base: seo/compare-cursor, so this PR merges cleanly after #48.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(ci): harden frontend lint and build pipeline

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
stevenfackley added a commit that referenced this pull request Apr 21, 2026
Fifth and final entry in batch D of the /compare series. Replit Agent
is the closest to StackAlchemist by *promise* on the "hosted vs owned"
axis — the honest cut is runtime and ownership.

- content/compare/replit-agent.md: founder-voice comparison. Clear on
  where Replit wins (hosted runtime, flexible stack, zero infra) vs.
  where StackAlchemist wins (owned repo on your GitHub, one-time price,
  production stack done well, compile gate).
- manifest: replit-agent entry with wins/verdict.
- /compare index: teaser now "Have a tool you want us to cover?"
  Remaining SEO plan /compare entries (Bubble, Retool) are low-priority
  low-code tools — deferred.

Batch D 3/3 — /compare is now feature-complete per the SEO plan.
Base: seo/compare-cursor, so this PR merges cleanly after #48.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
stevenfackley added a commit that referenced this pull request Apr 21, 2026
* feat(seo,compare): add /compare/replit-agent page

Fifth and final entry in batch D of the /compare series. Replit Agent
is the closest to StackAlchemist by *promise* on the "hosted vs owned"
axis — the honest cut is runtime and ownership.

- content/compare/replit-agent.md: founder-voice comparison. Clear on
  where Replit wins (hosted runtime, flexible stack, zero infra) vs.
  where StackAlchemist wins (owned repo on your GitHub, one-time price,
  production stack done well, compile gate).
- manifest: replit-agent entry with wins/verdict.
- /compare index: teaser now "Have a tool you want us to cover?"
  Remaining SEO plan /compare entries (Bubble, Retool) are low-priority
  low-code tools — deferred.

Batch D 3/3 — /compare is now feature-complete per the SEO plan.
Base: seo/compare-cursor, so this PR merges cleanly after #48.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* feat(platform): add tier 3 infra and byok settings

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
stevenfackley added a commit that referenced this pull request Apr 29, 2026
* feat(seo,compare): add /compare/cursor page

Fourth entry in the /compare series. Cursor sits in a different category
from v0/Bolt/Lovable — it is an AI-native IDE, not a prompt-to-app
generator. The honest answer is that the two are complementary, not
competitive: use StackAlchemist once to create the repo, then Cursor
forever after.

- content/compare/cursor.md: founder-voice comparison. Clear that Cursor
  is the best AI IDE, and that StackAlchemist does not compete with it
  once a repo exists. Positions the natural "use both" workflow.
- manifest: cursor entry with wins/verdict.
- /compare index: teaser now "Next up: Replit Agent".

Batch D 2/3.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* feat(seo,compare): add /compare/replit-agent page (#49)

* feat(seo,compare): add /compare/replit-agent page

Fifth and final entry in batch D of the /compare series. Replit Agent
is the closest to StackAlchemist by *promise* on the "hosted vs owned"
axis — the honest cut is runtime and ownership.

- content/compare/replit-agent.md: founder-voice comparison. Clear on
  where Replit wins (hosted runtime, flexible stack, zero infra) vs.
  where StackAlchemist wins (owned repo on your GitHub, one-time price,
  production stack done well, compile gate).
- manifest: replit-agent entry with wins/verdict.
- /compare index: teaser now "Have a tool you want us to cover?"
  Remaining SEO plan /compare entries (Bubble, Retool) are low-priority
  low-code tools — deferred.

Batch D 3/3 — /compare is now feature-complete per the SEO plan.
Base: seo/compare-cursor, so this PR merges cleanly after #48.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(ci): harden frontend lint and build pipeline

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
stevenfackley added a commit that referenced this pull request Jul 23, 2026
* fix(deps): bump brace-expansion 5.0.6 -> 5.0.7

Clears Dependabot alert #48 (high, vulnerable range >=3.0.0 <5.0.7).
Root instance satisfies minimatch ^5.0.5; nested 1.1.x eslint-chain
copies are outside the vulnerable range (refreshed to 1.1.16 by the
same npm update).

* fix(deps): floor sharp at 0.35.0+ via override — clears npm audit gate

The CI Audit Dependencies step failed on sharp <0.35.0 (libvips CVEs,
GHSA-f88m-g3jw-g9cj). npm audit displayed this as a wall of next
advisories, but that was the metavulnerability rollup: next was flagged
only for depending on vulnerable sharp. Flooring sharp (0.34.5 ->
0.35.3) takes npm audit to 0 vulnerabilities; no gate change needed.

Same sharp@0 override pattern as haulcall and trailtold.
stevenfackley added a commit that referenced this pull request Jul 23, 2026
* fix(deps): resolve known security vulnerabilities

Bump vulnerable dependencies flagged by the GitHub/OSV advisory database:
npm audit fixes, upward-only direct bumps, and scoped overrides for
transitive packages (brace-expansion, shell-quote, postcss, esbuild, ws,
undici, minimatch, glob, cookie); pnpm overrides; lockfile re-resolution.
No dependency was downgraded (verified against HEAD).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011ZwgeVpoxnDRL78Dw1bSu1

* fix(deps): repair lockfile consistency and override resolution

- Regenerate complete lockfiles with full npm install (npm ci was failing
  on missing entries from --package-lock-only updates)
- Constrain brace-expansion overrides per-major (1.1.16 / 2.1.2 / 5.0.7);
  the audit-fix '>=1.1.16' override was jumping minimatch's dependency
  across majors and breaking ESLint at runtime
- Cap vitest override at ~3.2.6 where vite 5 is in use (vitest 4 needs vite 6)
- ai-fit: add required TextArea props surfaced by react-native type bump

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011ZwgeVpoxnDRL78Dw1bSu1

* fix(deps): bump brace-expansion 5.0.6 -> 5.0.7 (#238)

* fix(deps): bump brace-expansion 5.0.6 -> 5.0.7

Clears Dependabot alert #48 (high, vulnerable range >=3.0.0 <5.0.7).
Root instance satisfies minimatch ^5.0.5; nested 1.1.x eslint-chain
copies are outside the vulnerable range (refreshed to 1.1.16 by the
same npm update).

* fix(deps): floor sharp at 0.35.0+ via override — clears npm audit gate

The CI Audit Dependencies step failed on sharp <0.35.0 (libvips CVEs,
GHSA-f88m-g3jw-g9cj). npm audit displayed this as a wall of next
advisories, but that was the metavulnerability rollup: next was flagged
only for depending on vulnerable sharp. Flooring sharp (0.34.5 ->
0.35.3) takes npm audit to 0 vulnerabilities; no gate change needed.

Same sharp@0 override pattern as haulcall and trailtold.

* fix(deps): resolve current security advisories (refreshed against latest main)

Rebuilt from today's main and today's advisory set: npm audit fixes,
upward-only direct bumps, per-major overrides for transitive packages,
pnpm override sanitation, uv.lock/cargo/requirements updates.
Verified: no dependency downgraded; lockfiles npm-ci-consistent.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011ZwgeVpoxnDRL78Dw1bSu1

---------

Co-authored-by: Claude <noreply@anthropic.com>
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.

1 participant