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-near-app

v8.0.0

Published

Quickly scaffold your dApp on NEAR Blockchain

Downloads

180

Readme

Create NEAR App

Gitpod Ready-to-Code

Quickly build apps backed by the NEAR blockchain

Prerequisites

Make sure you have a current version of Node.js installed – we are targeting versions 16+ for JS contracts and 18+ for frontend/gateways.

Read about other prerequisites in our docs.

Getting Started

To create a new NEAR project run this and follow interactive prompts:

npx create-near-app@latest

Follow the instructions in the README.md in the project you just created! 🚀

Contracts

You can create contracts written in:

  • Javascript
  • Rust

::: We strongly recommend you to follow our smart contract quickstart if you are new to NEAR contracts. :::

For testing we use a sandboxed environment. You can write the tests in JavaScript or Rust.

WebApps

You can create a web application in:

::: We strongly recommend you to follow our web app quickstart if you are new to NEAR WebApps. :::

Consider using pnpm to handle the frontend, since it is much faster than npm and yarn.

Using CLI arguments to run create-near-app

This CLI supports arguments to skip interactive prompts:

npx create-near-app
  <project-name>
  --frontend next-app|next-page|none
  --contract js|rs|none
  --install

Use --install to automatically install dependencies from all package.json files.

When using arguments, all arguments are required, except for --install.

Getting Help

Check out our documentation or chat with us on Discord. We'd love to hear from you!

Contributing to create-near-app

To make changes to create-near-app itself:

  • clone the repository (Windows users, use git clone -c core.symlinks=true)
  • in your terminal, enter one of the folders inside templates, such as templates/frontend/next-app
  • now you can run pnpm install to install dependencies and pnpm run dev to run the local development server, just like you can in a new app created with create-near-app

About commit messages

create-near-app uses semantic versioning and auto-generates nice release notes & a changelog all based off of the commits. We do this by enforcing Conventional Commits. In general the pattern mostly looks like this:

type(scope?): subject  #scope is optional; multiple scopes are supported (current delimiter options: "/", "\" and ",")

Real world examples can look like this:

chore: run tests with GitHub Actions

fix(server): send cors headers

feat(blog): add comment section

If your change should show up in release notes as a feature, use feat:. If it should show up as a fix, use fix:. Otherwise, you probably want refactor: or chore:. More info

Deploy create-near-app

If you want to deploy a new version, you will need two prerequisites:

  1. Get publish-access to the NPM package
  2. Get write-access to the GitHub repository
  3. Obtain a personal access token (it only needs the "repo" scope).
  4. Make sure the token is available as an environment variable called GITHUB_TOKEN

Then run one script:

npm run release

Or just release-it

License

This repository is distributed under the terms of both the MIT license and the Apache License (Version 2.0). See LICENSE and LICENSE-APACHE for details.