chore: add redirect packages for @rivetkit/actor & @rivetkit/core

[NathanFlurry]

No description provided.

[claude]

Claude finished @NathanFlurry's task —— View job

---

Code Review Progress

I'll review this PR that adds redirect packages for @rivetkit/actor and @rivetkit/core. Let me analyze the changes:

Review Tasks:

• Analyze the redirect package pattern implementation
• Review package.json configurations
• Check for potential breaking changes
• Verify README files follow project conventions
• Assess overall code quality and best practices
• Provide final review feedback

Code Review Summary

This PR successfully implements redirect packages for @rivetkit/actor and @rivetkit/core following the package consolidation in PR #1205. Here's my detailed assessment:

✅ Strengths

1. Clear Migration Strategy: Both redirect packages throw informative runtime errors that guide users to install rivetkit instead, providing an excellent developer experience during migration.

2. Consistent Implementation: Both packages follow identical patterns:

   • Runtime error messages clearly explain the migration
   • Package.json configurations are minimal and focused
   • README files provide clear migration instructions

3. Proper Package Structure:

   • Correct TypeScript configuration inheriting from workspace base
   • Proper build setup with tsup for both ESM and CJS outputs
   • Appropriate export configurations supporting both import styles

⚠️ Critical Issue: Breaking Changes Without Coordination

Major Concern: This PR will immediately break ALL examples and existing codebases that import from @rivetkit/actor or @rivetkit/core. I found 26+ files across the examples that still use these imports:

• examples/*/src/**/*.ts - All example source files
• examples/*/tests/**/*.ts - All test files
• README.md - Main documentation

Impact:

• Every example will fail to run after this PR merges
• Documentation becomes outdated immediately
• Existing user projects will break on next install

📋 Recommendations

1. Coordinate Updates: Either:

   • Include updates to all examples and documentation in this PR, OR
   • Create a follow-up PR immediately to update all references, OR
   • Consider a phased approach with deprecation warnings first

2. Package.json Enhancements: Consider adding:

   {
     "deprecated": "This package has been replaced by 'rivetkit'. Please install 'rivetkit' instead.",
     "keywords": ["deprecated", "rivetkit", "redirect"]
   }

3. README Improvements: Add installation commands:

   # Migration Guide
   
   **Old:**
   ```sh
   npm install @rivetkit/actor

   New:

   npm install rivetkit

4. Consider Gradual Deprecation: Instead of throwing errors immediately, consider:

   • Console warnings for 1-2 versions
   • Then runtime errors in subsequent versions

📋 Minor Issues

• README files don't follow the exact CLAUDE.md template (missing Discord/Issues links)
• Package versions at 0.0.0 might confuse dependency resolution

Overall Assessment

The redirect pattern implementation is technically sound and follows best practices. However, the immediate breaking change without coordinating updates to examples and documentation is a significant concern that should be addressed before merging.

Recommendation: Either update all examples/docs in this PR or create a follow-up PR immediately to prevent broken state in the repository.

---

[NathanFlurry]

• chore: symlink CLAUDE.md to AGENTS.md #1210
• fix(core): prevent calling onStateChange recurively when changing state from within onStateChange #1209
• fix(core): fix notifying onStateChange for non-state mutations to persisted state #1208
• chore: add redirect packages for @rivetkit/actor & @rivetkit/core #1207 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• merge queue - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[graphite-app]

Merge activity

• Sep 12, 5:08 PM UTC: NathanFlurry added this pull request to the Graphite merge queue.
• Sep 12, 5:09 PM UTC: CI is running for this pull request on a draft pull request (#1211) due to your merge queue CI optimization settings.
• Sep 12, 5:09 PM UTC: Merged by the Graphite merge queue via draft PR: #1211.