Gradual migration path from unstated

[loganvolkers]

The readme contains some promises about making sure that unstated-next fulfills all the needs of unstated users and that there is a clean migration path.

In reality we found that we don't have a clean path that doesn't involve a massive rewrite.

To facilitate a more gradual migration, I created unstated-retro.

@jamiebuilds looking for your feedback here. Read the FAQ at the bottom about a gradual "child-first" migration path.

[deg]

Is this working well already? It looks like it may be a great interim solution for my project.

[loganvolkers]

Yep we're using it in production. unstated-retro is the npm package

…

On Wed, Jan 8, 2020, 6:46 AM David Goldfarb ***@***.***> wrote: Is this working well already? It looks like it may be a great interim solution for my project. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#53?email_source=notifications&email_token=AAI2PXWGRT5R2FFN4METVY3Q4XRN7A5CNFSM4JB7VB22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIMY6EY#issuecomment-572100371>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAI2PXVYAMJ4GVZMXDEHZ33Q4XRN7ANCNFSM4JB7VB2Q> .