npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

create-terra-app

v0.10.0

Published

Set up a modern Cosmos app by running one command ⚛️

Downloads

5

Readme

create-cosmos-app

Set up a modern Cosmos app by running one command ⚛️

Demo

https://user-images.githubusercontent.com/545047/192061992-f0e1106d-f4b2-4879-ab0a-896f22ee4f49.mp4

Overview

# install
npm install -g create-cosmos-app

# run one command
create-cosmos-app

> name: my-app
cd my-app
yarn && yarn dev

# now your app is running on localhost:3000!

Get Started Immediately

You don’t need to install or configure cosmjs, keplr, nextjs, webpack or Babel.

Everything is preconfigured, ready-to-go, so you can focus on your code!

  • ⚡️ Connect easily to keplr + keplr mobile via wallet connect
  • ⚛️ Sign and broadcast with cosmjs stargate + cosmwasm signers
  • 🛠 Render pages with next.js hybrid static & server rendering
  • 🎨 Build awesome UI with Cosmos Kit and Chakra UI
  • 📝 Leverage chain-registry for Chain and Asset info for all Cosmos chains

Education & Resources

🎥 Checkout our videos to learn to learn more about create-cosmos-app and tooling for building frontends in the Cosmos!

Checkout cosmos-kit for more docs as well as cosmos-kit/react for getting cosmjs stargate and cosmjs signers.

Creating an App

To create a new app, you may choose one of the following methods:

global install

npm install -g create-cosmos-app

Then run the command:

create-cosmos-app

we also made an alias cca if you don't want to type create-cosmos-app:

cca

npx

npx create-cosmos-app

npm

npm init cosmos-app 

Yarn

yarn create cosmos-app 

Examples

Explore examples!

cca --example

Send Tokens

cca --name cca-sendtokens --example --template send-tokens

Osmosis

uses osmojs

cca --name myosmoapp --example --template osmosis

or the cosmwasm example:

cca --name osmowasm --example --template osmosis-cosmwasm

Juno

uses juno-network

cca --name myjunoapp --example --template juno

Stargaze

uses stargazejs

cca --name mystarsapp --example --template stargaze

CosmWasm

cca --name mywasmapp --example --template cosmwasm

Tailwind

cca --name cca-tailwind --example --template tailwindcss

Development

Because the nature of how template boilerplates are generated, we generate yarn.lock files inside of nested packages so we can fix versions to avoid non-deterministic installations.

When adding packages, yarn workspaces will use the root yarn.lock. It could be ideal to remove it while adding packages, and when publishing or pushing new changes, generating the nested lock files.

In the root, to remove all nested lock files:

yarn locks:remove

When you need to remove/generate locks for all nested packages, simply run yarn locks in the root:

yarn locks

Credits

🛠 Built by Cosmology — if you like our tools, please consider delegating to our validator ⚛️

Code built with the help of these related projects: