Maintain Effect v3 to v4 Migration Guidance
When to Use
Keep Effect v3-to-v4 migration annotations and generated guidance aligned with verified public API replacements.
Workflow
Inventory affected v3 modules and names. Verify proposed v4 replacements through implementation, tests and a representative consumer call. Note behavior differences, service requirements and unsupported mappings. Update source annotations under the checkout's migration policy. Generate from the required committed revision, inspect for unrelated movement and stale refs, and document when generation is deferred for uncommitted code.
Example
Record a moved v3 API and compile the suggested v4 call before updating the generated migration guide.
Limitations
Requires the relevant Effect workspace and its versioned tools. Use local project policy and authorized fixtures. Results cover only the checked packages and environments.
Bundled resources
Use the bundled local references for the applicable branch of the workflow: annotations, generation. Run commands against the target Effect workspace.
Source
Adapted from the pinned skill tree. See the MIT license.
This snapshot of Effect v4 is vendored by Local Studio.