Enum wasm_pack::command::Command

pub enum Command {
    Build(BuildOptions),
    Pack {
        path: Option<PathBuf>,
    },
    Generate {
        name: String,
        template: String,
        mode: InstallMode,
    },
    Publish {
        target: String,
        access: Option<Access>,
        tag: Option<String>,
        path: Option<PathBuf>,
    },
    Login {
        registry: Option<String>,
        scope: Option<String>,
        always_auth: bool,
        auth_type: Option<String>,
    },
    Test(TestOptions),
}

The various kinds of commands that wasm-pack can execute.

Variants

Build(BuildOptions)

🏗️ build your npm package!

Pack

Fields

path: Option<PathBuf>

The path to the Rust crate. If not set, searches up the path from the current dirctory.

🍱 create a tar of your npm package but don’t publish!

Generate

Fields

name: String

The name of the project

template: String

The URL to the template

mode: InstallMode

Should we install or check the presence of binary tools. [possible values: no-install, normal, force]

🐑 create a new project with a template

Publish

Fields

target: String

Sets the target environment. [possible values: bundler, nodejs, web, no-modules]

access: Option<Access>

The access level for the package to be published

tag: Option<String>

The distribution tag being used for publishing. See https://docs.npmjs.com/cli/dist-tag

path: Option<PathBuf>

The path to the Rust crate. If not set, searches up the path from the current dirctory.

🎆 pack up your npm package and publish!

Login

Fields

registry: Option<String>

Default: ‘https://registry.npmjs.org/’. The base URL of the npm package registry. If scope is also specified, this registry will only be used for packages with that scope. scope defaults to the scope of the project directory you’re currently in, if any.

scope: Option<String>

Default: none. If specified, the user and login credentials given will be associated with the specified scope.

always_auth: bool

If specified, save configuration indicating that all requests to the given registry should include authorization information. Useful for private registries. Can be used with –registry and / or –scope

auth_type: Option<String>

Default: ‘legacy’. Type: ‘legacy’, ‘sso’, ‘saml’, ‘oauth’. What authentication strategy to use with adduser/login. Some npm registries (for example, npmE) might support alternative auth strategies besides classic username/password entry in legacy npm.

👤 Add an npm registry user account! (aliases: adduser, add-user)

Test(TestOptions)

👩‍🔬 test your wasm!

Trait Implementations

impl Debug for Command

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl StructOpt for Command

fn clap<'a, 'b>() -> App<'a, 'b>

Returns clap::App corresponding to the struct.

fn from_clap(matches: &ArgMatches<'_>) -> Self

Builds the struct from clap::ArgMatches. It’s guaranteed to succeed if matches originates from an App generated by StructOpt::clap called on the same type, otherwise it must panic.

fn from_args() -> Self

Builds the struct from the command line arguments (std::env::args_os). Calls clap::Error::exit on failure, printing the error message and aborting the program.

fn from_args_safe() -> Result<Self, Error>

Builds the struct from the command line arguments (std::env::args_os). Unlike StructOpt::from_args, returns clap::Error on failure instead of aborting the program, so calling .exit is up to you.

fn from_iter<I>(iter: I) -> Self where
    I: IntoIterator,
    <I as IntoIterator>::Item: Into<OsString>,
    <I as IntoIterator>::Item: Clone, 

Gets the struct from any iterator such as a Vec of your making. Print the error message and quit the program in case of failure.

fn from_iter_safe<I>(iter: I) -> Result<Self, Error> where
    I: IntoIterator,
    <I as IntoIterator>::Item: Into<OsString>,
    <I as IntoIterator>::Item: Clone, 

Gets the struct from any iterator such as a Vec of your making.