Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://rustwasm.github.io/docs/wasm-pack/prerequisites/npm.html below:

npm (optional) - Hello wasm-pack!

1. 1. Introduction
2. 2. Quickstart
3. 3. Prerequisites
4. 1. 3.1. npm (optional)
   2. 3.2. considerations
   3. 3.3. Non-rustup setups
5. 4. Commands
6. 1. 4.1. new
   2. 4.2. build
   3. 4.3. test
   4. 4.4. pack and publish
   5. 4.5. init (DEPRECATED)
7. 5. Tutorials
8. 1. 5.1. Hybrid applications with Webpack
   2. 1. 5.1.1. Getting started
      2. 5.1.2. Using your library
   3. 5.2. npm browser packages
   4. 1. 5.2.1. Getting started
      2. 1. 5.2.1.1. Manual Setup
      3. 5.2.2. Template deep dive
      4. 1. 5.2.2.1. Cargo.toml
         2. 5.2.2.2. src/lib.rs
         3. 5.2.2.3. src/utils.rs
         4. 5.2.2.4. wee_alloc
         5. 5.2.2.5. tests/web.rs
      5. 5.2.3. Building your project
      6. 5.2.4. Testing your project
      7. 5.2.5. Packaging and publishing
      8. 5.2.6. Using your library
9. 6. Cargo.toml Configuration
10. 7. Contributing

Currently, wasm-pack requires that you have npm installed to pack and publish your package. Longterm, this will be replaced by a Rust only version.

If you would rather use another package manager that interfaces with the npm registry you may, however, the pack, publish, and login commands wrap the npm CLI interface and as a result require that npm be installed.

You can install npm by following these instructions.

Part of the wasm-pack workflow is to publish your package to the npm Registry.

Regardless of which package manager CLI tool you prefer, if you wish to publish your package to the npm registry you'll need an npm account.

You can find information about signing up for npm here.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4