No matching version found for automerge-wasm@0.1.7

[ccorcos]

I'm having an issue installing...

 ❯❯❯ npm i --save automerge
npm ERR! code ETARGET
npm ERR! notarget No matching version found for automerge-wasm@0.1.7.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/chet/.npm/_logs/2022-11-06T11_04_11_938Z-debug-0.log

[ccorcos]

Well this worked:

❯❯❯ npm i --save automerge@1.0.1-preview.6

[a2f0]

@ccorcos I had the same issue and ended up on the automerge Slack instance to talk about it (ref). I ended up speaking with one of the core developers and he suggested to use npm i @automerge/automerge

[pvh]

Yes! Automerge 2.0 is very close to a release at which point we'll add a proper deprecation note to the old package name. Let us know how things go with the new version. We're currently resolving a performance regression so expect at least one more beta before the release.

[ccorcos]

@pvh same api and everything? Where's the source code for 2.0?

[alexjg]

2.0 is implemented in Rust at https://github.com/automerge/automerge-rs

[pvh]

But the package you're looking for is available at ***@***.***/automerge` in npm.

…

On Tue, Nov 15, 2022 at 4:18 AM alexjg ***@***.***> wrote: 2.0 is implemented in Rust at https://github.com/automerge/automerge-rs — Reply to this email directly, view it on GitHub <automerge/automerge#517 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAAWQBBD2B2NSV557EX53TWIN5QFANCNFSM6AAAAAARYL57FU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Peter van Hardenberg "Everything was beautiful, and nothing hurt."—Kurt Vonnegut