Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Remove package cosmwasm-launchpad

See original GitHub issue

Nobody seems to be using this.

Let cosmwasm-stargate not depend on cosmwasm-launchpad anymore (#848)
Merge packages/cli/examples/coralnet.ts and packages/cli/examples/helpers.ts into a new CosmWasm+Stargatre example (#849)
Delete cosmwasm-launchpad from repo (850)
Mark @cosmjs/cosmwasm-launchpad and @cosmjs/cosmwasm as deprecated on npm

Issue Analytics

State:
Created 2 years ago
Comments:10 (9 by maintainers)

Top GitHub Comments

1reaction

webmaster128commented, Jun 9, 2021

Given that Secret uses a fork of CosmJS anyways and there is great potential to reuse latest upstream dependencies, we’ll remove the package now. I think replacing some of the higher level functionality with a fork while building on top of lower level CosmJS packages is a solid long term solution.

1reaction

ethanfreycommented, May 4, 2021

Correction: x/wasm versions. Of course we expect you to embed it in your app (and I think you swap out with a custom wasmvm which is great for your use case). The main point is it is tested with a certain set of messages and queries and handlers and if those differ, the CosmJS code may not match.

With stargate we put more effort into making it generic. Thus, you could import all the standard components and build SigningSecretClient on those same basic points, not wrapping SigningCosmWasmClient but at the same level as it. That means, just one package for you to maintain and the rest is upstream.