fork of https://github.com/rustwasm/wasm-pack for the needs of NextGraph.org
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Ashley Williams e67f835867 feat(build): integrate cargo build and wasm-bindgen steps 7 years ago
examples/js-hello-world feat(example): add js-hello-world example 7 years ago
src feat(build): integrate cargo build and wasm-bindgen steps 7 years ago
tests feat(args): take a path to a crate as an arg to init 7 years ago
.gitignore feat(pkg): do it in a dir 7 years ago
.travis.yml feat(test): only use stable for now cuz cargo fmt 7 years ago
CONTRIBUTING.md feat(doc): add contributing.md 7 years ago
Cargo.lock feat: split into lib, test 7 years ago
Cargo.toml feat(pkg): support license, repo 7 years ago
LICENSE-APACHE feat(doc): add licenses 7 years ago
LICENSE-MIT feat(doc): add licenses 7 years ago
README.md feat(doc): doc available commands 7 years ago

README.md

📦 wasm-pack

pack up the wasm and publish it to npm!

Build Status

the goal of this project is to create a portable command line tool for publishing compiled wasm projects to the npm registry for the consumption of js devs using the npm CLI, yarn, or any other CLI tool that interfaces with the npm registry.

this project is a part of the rust-wasm group. you can find more info by visiting that repo!

🔮 prerequisities

this project is written in rust. get rust to work on this project.

🏃 up and running

  1. fork and clone this repository
  2. cd wasm-pack
  3. cargo run

💃 commands

  • help: display available commands
  • 🐣 init:
    • generate a package.json
    • run wasm-bindgen [NOT IMPLEMENTED]
  • 🍱 pack: create a tarball but don't push to the npm registry [NOT IMPLEMENTED]
  • 🎆 publish: create a tarball and publish to the npm registry [NOT IMPLEMENTED]

what's it do?

right now? not much. here's the plan:

  • read data from Cargo.toml
  • run wasm-bindgen
  • read JS dependency data from your compiled wasm (see rust-wasm/36)
  • write data to package.json
  • log you in to npm
  • publish package to npm registry