[ { "path": ".github/ISSUE_TEMPLATE/bug_report.md", "content": "---\nname: Bug Report šŸ›\nabout: Did something not work as expected?\n---\n\n## šŸ› Bug description\nDescribe your issue in detail.\n\n#### šŸ¤” Expected Behavior\nWhat should have happened?\n\n#### šŸ‘Ÿ Steps to reproduce\nClear steps describing how to reproduce the issue, including commands and flags run. If you are seeing an error, please include the full error message and stack trace.\n\n#### šŸŒ Your environment\nInclude the relevant details of your environment.\nwasm-pack version:\nrustc version:" }, { "path": ".github/ISSUE_TEMPLATE/feature_request.md", "content": "---\nname: Feature Request šŸ’”\nabout: Suggest a new idea for wasm-pack\n---\n\n## šŸ’” Feature description\nBrief explanation of the requested feature.\n\n#### šŸ’» Basic example\nInclude a basic code example if possible. Omit this section if not applicable." }, { "path": ".github/PULL_REQUEST_TEMPLATE.md", "content": "Make sure these boxes are checked! šŸ“¦āœ…\n\n- [ ] You have the latest version of `rustfmt` installed\n```bash\n$ rustup component add rustfmt\n```\n- [ ] You ran `cargo fmt` on the code base before submitting\n- [ ] You reference which issue is being closed in the PR text\n\nāœØāœØ šŸ˜„ Thanks so much for contributing to wasm-pack! šŸ˜„ āœØāœØ\n" }, { "path": ".github/workflows/approve.yml", "content": "name: Automatic Approve\npermissions:\n contents: read\n pull-requests: write\non:\n schedule: \n - cron: \"0 0 * * *\"\n workflow_dispatch:\njobs:\n automatic-approve:\n name: Automatic Approve\n runs-on: ubuntu-latest\n steps:\n - name: Automatic Approve\n uses: mheap/automatic-approve-action@v1.1.0\n with:\n token: ${{ secrets.GITHUB_TOKEN }}\n workflows: \"test.yml\"\n" }, { "path": ".github/workflows/book.yml", "content": "name: Build and deploy documentation book\n\non:\n push:\n pull_request: \n\njobs:\n book:\n permissions:\n contents: write\n name: Build and deploy book\n runs-on: ubuntu-latest\n steps:\n - uses: actions/checkout@v3\n - uses: dtolnay/rust-toolchain@stable\n with:\n toolchain: stable\n\n - name: Cache dependencies\n uses: actions/cache@v3\n env:\n cache-name: cache-mdbook\n with:\n path: |\n ~/.cargo/.crates.toml\n ~/.cargo/.crates2.json\n ~/.cargo/bin\n ~/.cargo/registry/index\n ~/.cargo/registry/cache\n key: ${{ runner.os }}-build-${{ env.cache-name }}-0.3 }}\n\n - name: Install mdbook\n run: |\n (test -x $HOME/.cargo/bin/cargo-install-update || cargo install cargo-update)\n (test -x $HOME/.cargo/bin/mdbook || cargo install --vers \"^0.4\" mdbook)\n cargo install-update -a\n\n - name: Build book\n run: |\n mdbook --version\n (cd docs && mv _theme theme && mdbook build)\n rustc ./docs/_installer/build-installer.rs\n ./build-installer\n\n - name: Deploy book\n uses: JamesIves/github-pages-deploy-action@v4.4.1\n if: ${{ github.ref == 'refs/heads/master' }}\n with:\n branch: gh-pages\n folder: docs\n token: ${{ secrets.GITHUB_TOKEN }}\n single-commit: true\n" }, { "path": ".github/workflows/release.yml", "content": "on:\n push:\n tags:\n - 'v*' # Run when tag matches v*, i.e. v1.0, v20.15.10\n\nname: Release\npermissions:\n contents: read\n\nenv:\n RELEASE_BIN: wasm-pack\n RELEASE_DIR: artifacts\n GITHUB_REF: '${{ github.ref }}'\n WINDOWS_TARGET: x86_64-pc-windows-msvc\n MACOS_AMD64_TARGET: x86_64-apple-darwin\n MACOS_ARM64_TARGET: aarch64-apple-darwin\n LINUX_AMD64_TARGET: x86_64-unknown-linux-musl\n LINUX_ARM64_TARGET: aarch64-unknown-linux-musl\n\n # Space separated paths to include in the archive.\n RELEASE_ADDS: README.md LICENSE-APACHE LICENSE-MIT\n\njobs:\n build:\n name: Build artifacts\n runs-on: ${{ matrix.os }}\n strategy:\n matrix:\n include:\n - target: x86_64-unknown-linux-musl\n os: ubuntu-latest\n rust: stable\n - target: aarch64-unknown-linux-musl\n os: ubuntu-latest\n rust: stable\n - target: x86_64-apple-darwin\n os: macos-latest\n rust: stable\n - target: aarch64-apple-darwin\n os: macos-latest\n rust: stable\n - target: x86_64-pc-windows-msvc\n os: windows-latest\n rust: stable\n\n steps:\n - uses: actions/checkout@v3\n - uses: dtolnay/rust-toolchain@stable\n with:\n toolchain: ${{ matrix.rust }}\n targets: wasm32-unknown-unknown\n\n - name: Query version number\n id: get_version\n shell: bash\n run: |\n echo \"using version tag ${GITHUB_REF:10}\"\n echo ::set-output name=version::\"${GITHUB_REF:10}\"\n\n - name: Install C compilation tooling (Linux)\n if: matrix.os == 'ubuntu-latest'\n run: |\n sudo apt-get update -y\n sudo apt-get install clang gcc-aarch64-linux-gnu musl-tools -y\n\n - name: Install p7zip (MacOS)\n if: matrix.os == 'macos-latest'\n run: brew install p7zip\n\n - name: Add rustup target\n run: rustup target add ${{ matrix.target }}\n\n - uses: taiki-e/install-action@v2\n with:\n tool: cross\n\n - name: Build\n run: cross build --release --target ${{ matrix.target }}\n\n - name: Set RUSTFLAGS (Windows)\n if: matrix.os == 'windows-latest'\n run: echo \"RUSTFLAGS=-Ctarget-feature=+crt-static\" >> $GITHUB_ENV\n\n - name: Create artifact directory\n run: |\n mkdir ${{ env.RELEASE_DIR }}\n mkdir -p ${{ env.RELEASE_DIR }}/${{ env.RELEASE_BIN }}-${{ steps.get_version.outputs.VERSION }}-${{ matrix.target }}\n\n - name: Move binaries (Linux/MacOS)\n if: matrix.os == 'ubuntu-latest' || matrix.os == 'macos-latest'\n run: |\n mv ./target/${{ matrix.target }}/release/${{ env.RELEASE_BIN }} ${{ env.RELEASE_DIR }}/${{ env.RELEASE_BIN }}-${{ steps.get_version.outputs.VERSION }}-${{ matrix.target }}/${{ env.RELEASE_BIN }}\n mv ${{ env.RELEASE_ADDS }} ./${{ env.RELEASE_DIR }}/${{ env.RELEASE_BIN }}-${{ steps.get_version.outputs.VERSION }}-${{ matrix.target }}\n\n - name: Move binaries (Windows)\n if: matrix.os == 'windows-latest'\n shell: bash\n run: |\n cp ./target/${{ matrix.target }}/release/${{ env.RELEASE_BIN }}.exe ./${{ env.RELEASE_DIR }}/${{ env.RELEASE_BIN }}-${{ steps.get_version.outputs.VERSION }}-${{ matrix.target }}/${{ env.RELEASE_BIN }}.exe\n cp ./target/${{ matrix.target }}/release/${{ env.RELEASE_BIN }}.exe wasm-pack-init.exe\n mv ${{ env.RELEASE_ADDS }} ./${{ env.RELEASE_DIR }}/${{ env.RELEASE_BIN }}-${{ steps.get_version.outputs.VERSION }}-${{ matrix.target }}\n mv wasm-pack-init.exe ${{ env.RELEASE_DIR }}\n\n - name: Create tarball\n shell: bash\n run: 7z a -ttar -so -an ./${{ env.RELEASE_DIR }}/${{ env.RELEASE_BIN }}-${{ steps.get_version.outputs.VERSION }}-${{ matrix.target }} | 7z a -si ./${{ env.RELEASE_DIR }}/${{ env.RELEASE_BIN }}-${{ steps.get_version.outputs.VERSION }}-${{ matrix.target }}.tar.gz\n\n - name: Upload Zip\n uses: actions/upload-artifact@v4\n with:\n name: ${{ matrix.target }}\n path: ./${{ env.RELEASE_DIR }}\n\n release:\n name: GitHub Release\n needs: build\n permissions:\n contents: write\n runs-on: ubuntu-latest\n steps:\n - name: Query version number\n id: get_version\n shell: bash\n run: |\n echo \"using version tag ${GITHUB_REF:10}\"\n echo ::set-output name=version::\"${GITHUB_REF:10}\"\n\n - name: Create Release\n id: create_release\n uses: actions/create-release@v1\n env:\n GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n with:\n tag_name: ${{ steps.get_version.outputs.VERSION }}\n release_name: ${{ steps.get_version.outputs.VERSION }}\n\n - name: Download Linux amd64 tarball\n uses: actions/download-artifact@v4.1.7\n with:\n name: ${{ env.LINUX_AMD64_TARGET }}\n\n - name: Download Linux arm64 tarball\n uses: actions/download-artifact@v4.1.7\n with:\n name: ${{ env.LINUX_ARM64_TARGET }}\n\n - name: Download Windows tarball\n uses: actions/download-artifact@v4.1.7\n with:\n name: ${{ env.WINDOWS_TARGET }}\n\n - name: Download ARM64 MacOS tarball\n uses: actions/download-artifact@v4.1.7\n with:\n name: ${{ env.MACOS_ARM64_TARGET }}\n - name: Download AMD64 MacOS tarball\n uses: actions/download-artifact@v4.1.7\n with:\n name: ${{ env.MACOS_AMD64_TARGET }}\n\n - name: Release Linux amd64 tarball\n uses: actions/upload-release-asset@v1\n env:\n GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n with:\n upload_url: ${{ steps.create_release.outputs.upload_url }}\n asset_path: ./wasm-pack-${{ steps.get_version.outputs.VERSION }}-${{ env.LINUX_AMD64_TARGET }}.tar.gz\n asset_content_type: application/gzip\n asset_name: wasm-pack-${{ steps.get_version.outputs.VERSION }}-${{ env.LINUX_AMD64_TARGET }}.tar.gz\n\n - name: Release Linux arm64 tarball\n uses: actions/upload-release-asset@v1\n env:\n GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n with:\n upload_url: ${{ steps.create_release.outputs.upload_url }}\n asset_path: ./wasm-pack-${{ steps.get_version.outputs.VERSION }}-${{ env.LINUX_ARM64_TARGET }}.tar.gz\n asset_content_type: application/gzip\n asset_name: wasm-pack-${{ steps.get_version.outputs.VERSION }}-${{ env.LINUX_ARM64_TARGET }}.tar.gz\n\n - name: Release Windows tarball\n uses: actions/upload-release-asset@v1\n env:\n GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n with:\n upload_url: ${{ steps.create_release.outputs.upload_url }}\n asset_path: ./wasm-pack-${{ steps.get_version.outputs.VERSION }}-${{ env.WINDOWS_TARGET }}.tar.gz\n asset_content_type: application/gzip\n asset_name: wasm-pack-${{ steps.get_version.outputs.VERSION }}-${{ env.WINDOWS_TARGET }}.tar.gz\n\n - name: Release Windows init exe\n uses: actions/upload-release-asset@v1\n env:\n GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n with:\n upload_url: ${{ steps.create_release.outputs.upload_url }}\n asset_path: ./wasm-pack-init.exe\n asset_content_type: application/vnd.microsoft.portable-executable\n asset_name: wasm-pack-init.exe\n\n - name: Release AMD64 MacOS tarball\n uses: actions/upload-release-asset@v1\n env:\n GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n with:\n upload_url: ${{ steps.create_release.outputs.upload_url }}\n asset_path: ./wasm-pack-${{ steps.get_version.outputs.VERSION }}-${{ env.MACOS_AMD64_TARGET }}.tar.gz\n asset_content_type: application/gzip\n asset_name: wasm-pack-${{ steps.get_version.outputs.VERSION }}-${{ env.MACOS_AMD64_TARGET }}.tar.gz\n - name: Release ARM64 MacOS tarball\n uses: actions/upload-release-asset@v1\n env:\n GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n with:\n upload_url: ${{ steps.create_release.outputs.upload_url }}\n asset_path: ./wasm-pack-${{ steps.get_version.outputs.VERSION }}-${{ env.MACOS_ARM64_TARGET }}.tar.gz\n asset_content_type: application/gzip\n asset_name: wasm-pack-${{ steps.get_version.outputs.VERSION }}-${{ env.MACOS_ARM64_TARGET }}.tar.gz\n" }, { "path": ".github/workflows/test.yml", "content": "name: Tests\non:\n push:\n branches:\n - master\n pull_request:\n branches:\n - master\njobs:\n test:\n name: Test\n permissions:\n contents: read\n runs-on: ${{ matrix.os }}\n strategy:\n matrix:\n build: [linux-stable, macos-stable, windows-stable]\n include:\n - build: linux-stable\n os: ubuntu-latest\n rust: stable\n - build: macos-stable\n os: macos-latest\n rust: stable\n - build: windows-stable\n os: windows-latest\n rust: stable\n steps:\n - uses: actions/checkout@v4\n - uses: nanasess/setup-chromedriver@master\n - if: matrix.os == 'macos-latest'\n run: brew install --cask firefox\n - uses: dtolnay/rust-toolchain@stable\n with:\n toolchain: ${{ matrix.rust }}\n targets: wasm32-unknown-unknown\n - uses: actions/setup-node@v3\n - name: Cache dependencies\n uses: actions/cache@v4\n with:\n path: |\n ~/.cargo/.crates.toml\n ~/.cargo/.crates2.json\n ~/.cargo/bin\n ~/.cargo/registry/index\n ~/.cargo/registry/cache\n target\n key: ${{ runner.os }}-build-${{ hashFiles('Cargo.lock') }}\n - name: Run Tests\n run: cargo test --all --locked\n env:\n RUST_BACKTRACE: 1\n - name: Clippy\n run: cargo clippy\n - name: Cargo fmt\n run: cargo fmt --all -- --check\n" }, { "path": ".gitignore", "content": "target/\n**/*.rs.bk\ntests/.crates.toml\ntests/bin\n/build-installer\ndocs/book\ndocs/installer\n\n.idea\n" }, { "path": "CHANGELOG.md", "content": "# Changelog\n\n## šŸ¤ Unreleased\n\n## šŸŒ» 0.14.0\n\n- ### āœØ Features\n\n - **Support arbitrary wasm targets (WASI support) - [RReverser], [pull/1524]**\n\n Allows building for targets other than wasm32-unknown-unknown, enabling WASI and other custom wasm targets.\n\n [pull/1524]: https://github.com/drager/wasm-pack/pull/1524\n [RReverser]: https://github.com/RReverser\n\n - **macOS ARM (aarch64-apple-darwin) build support - [kaleidawave], [pull/1529]**\n\n Adds native Apple Silicon support in release builds and NPM package.\n\n [pull/1529]: https://github.com/drager/wasm-pack/pull/1529\n [kaleidawave]: https://github.com/kaleidawave\n\n - **Allow `--split-linked-modules` flag for wasm-bindgen - [codeart1st], [pull/1443]**\n\n [pull/1443]: https://github.com/drager/wasm-pack/pull/1443\n [codeart1st]: https://github.com/codeart1st\n\n - **Custom build profile support - [rafaelbeckel], [pull/1428]**\n\n Allows using custom cargo profiles via `--profile`.\n\n [pull/1428]: https://github.com/drager/wasm-pack/pull/1428\n [rafaelbeckel]: https://github.com/rafaelbeckel\n\n- ### šŸ¤• Fixes\n\n - **Fix NPM package download URL - [qinyuhang], [pull/1543]**\n\n [pull/1543]: https://github.com/drager/wasm-pack/pull/1543\n [qinyuhang]: https://github.com/qinyuhang\n\n - **Filter build artifacts to only .wasm files - [drager], [pull/1535]**\n\n [pull/1535]: https://github.com/drager/wasm-pack/pull/1535\n\n - **Handle undefined VERSION in installer script - [BrianHung], [pull/1512]**\n\n [pull/1512]: https://github.com/drager/wasm-pack/pull/1512\n [BrianHung]: https://github.com/BrianHung\n\n - **Fix it_gets_wasm_bindgen_version test - [mshroyer], [pull/1509]**\n\n [pull/1509]: https://github.com/drager/wasm-pack/pull/1509\n [mshroyer]: https://github.com/mshroyer\n\n- ### šŸ› ļø Maintenance\n\n - **Update dependencies to latest versions - [drager], [pull/1536]**\n\n [pull/1536]: https://github.com/drager/wasm-pack/pull/1536\n\n - **Security workflow permissions fixes - [drager]**\n\n - **Bump ring from 0.17.8 to 0.17.14 - [dependabot], [pull/1516]**\n\n [pull/1516]: https://github.com/drager/wasm-pack/pull/1516\n\n - **Bump brace-expansion from 1.1.11 to 1.1.12 in /npm - [dependabot], [pull/1515]**\n\n [pull/1515]: https://github.com/drager/wasm-pack/pull/1515\n\n - **Bump rustls from 0.23.16 to 0.23.18 - [dependabot], [pull/1451]**\n\n [pull/1451]: https://github.com/drager/wasm-pack/pull/1451\n [dependabot]: https://github.com/apps/dependabot\n\n - **Fix tar vulnerability (CVE-2026-23745) in npm package**\n\n Override tar dependency to ^7.5.3 to fix arbitrary file overwrite and symlink poisoning vulnerability ([GHSA-8qq5-rm4j-mr97]).\n\n [GHSA-8qq5-rm4j-mr97]: https://github.com/advisories/GHSA-8qq5-rm4j-mr97\n\n - **Fix axios vulnerabilities in npm package**\n\n Override axios dependency to ^0.30.0 to fix SSRF/credential leakage via absolute URL and XSRF-TOKEN leakage (CSRF) vulnerabilities.\n\n- ### šŸ“– Documentation\n\n - **Update documentation links to drager's repo - [yutannihilation], [pull/1513]**\n\n [pull/1513]: https://github.com/drager/wasm-pack/pull/1513\n [yutannihilation]: https://github.com/yutannihilation\n\n - **Document prerequisites for webdriver tests - [mshroyer], [pull/1509]**\n\n## ā˜€ļø 0.13.1\n\n- ### āœØ Features\n\n - **Requests using proxy settings from env - [jjyr], [pull/1438]**\n\n This enables ureq to use proxy settings from env, it solves lots of pain in network restricted environments.\n\n [pull/1438]: https://github.com/rustwasm/wasm-pack/pull/1438\n [jjyr]: https://github.com/jjyr\n\n- ### šŸ¤• Fixes\n\n - **Update binary-install to v0.4.1 - [drager], [pull/1407]**\n\n Release v0.4.0 of binary-install introduced a regression that caused failures on some platforms. This release fixes that regression.\n\n [pull/1407]: https://github.com/rustwasm/wasm-pack/pull/1407\n [drager]: https://github.com/drager\n\n - ** Allow npm binary upgrades - [net], [pull/1439]**\n\n Fixes an issue where upgrading `wasm-pack` via NPM would not update the underlying binary.\n Previously, the binary was stored in the `binary-install` package's directory without versioning, causing version upgrades to silently fail as the old binary continued to be used.\n The binary is now stored in `node_modules/wasm-pack/binary/`, ensuring proper version updates when upgrading the package.\n\n **Before:** Upgrading from `0.12.1` to `0.13.0` would continue using the `0.12.1` binary\n **After:** Each `wasm-pack` version manages its own binary, enabling proper version upgrades\n\n [pull/1439]: https://github.com/rustwasm/wasm-pack/pull/1439\n [net]: https://github.com/net\n\n- ### šŸ› ļø Maintenance\n\n - ** Remove unmaintained dependency atty in favor of stdlib - [mariusvniekerk], [pull/1436]**\n\n [pull/1436]: https://github.com/rustwasm/wasm-pack/pull/1436\n [mariusvniekerk]: https://github.com/mariusvniekerk\n\n## ā˜€ļø 0.13.0\n\n- ### āœØ Features\n\n - **Add option to skip optimization with wasm-opt - [sisou], [pull/1321]**\n\n This feature introduces the `--no-opt` option to wasm-pack, providing a significant improvement in build efficiency for projects requiring multiple wasm-pack executions.\n\n [pull/1321]: https://github.com/rustwasm/wasm-pack/pull/1321\n [sisou]: https://github.com/sisou\n\n - **Add support geckodriver for linux-aarch64 - [EstebanBorai], [pull/1371]**\n\n Introduces support to download Geckodriver in Linux aarch64.\n\n [pull/1371]: https://github.com/rustwasm/wasm-pack/pull/1371\n [EstebanBorai]: https://github.com/EstebanBorai\n\n - **Add wasm-opt linux aarch64 condition - [dkristia], [issue/1392], [pull/1393]**\n\n A linux aarch64 build for wasm-opt exists in the newest binaryen versions.\n\n [issue/1392]: https://github.com/rustwasm/wasm-pack/issues/1392\n [pull/1393]: https://github.com/rustwasm/wasm-pack/pull/1393\n [dkristia]: https://github.com/dkristia\n\n- ### šŸ¤• Fixes\n\n - **Fix passing relative paths to cargo - [dfaust], [issue/704], [issue/1156], [issue/1252], [pull/1331]**\n\n When building a crate located in a sub-directory, relative paths, passed as extra options to cargo (like `--target-dir`), are now handled correctly.\n\n [issue/704]: https://github.com/rustwasm/wasm-pack/issues/704\n [issue/1156]: https://github.com/rustwasm/wasm-pack/issues/1156\n [issue/1252]: https://github.com/rustwasm/wasm-pack/issues/1252\n [pull/1331]: https://github.com/rustwasm/wasm-pack/pull/1331\n [dfaust]: https://github.com/dfaust\n\n - **Rewrite wasm_target to use target-libdir - [daidoji], [issue/1342], [pull/1343]**\n\n Rewritten wasm_target to use target libdir from the rustc tool rather than looking through sysroot. This is to accomodate non-rustup installations.\n\n [issue/1342]: https://github.com/rustwasm/wasm-pack/issues/1342\n [pull/1343]: https://github.com/rustwasm/wasm-pack/pull/1343\n [daidoji]: https://github.com/daidoji\n\n - **Declare ES module in package.json - [gthb], [issue/1039], [pull/1061]**\n\n In bundler mode, generate package.json with \"type\": \"module\" and use the \"main\" attribute instead of the \"module\" attribute.\n\n This change makes the built ES module palatable to Node.js (when run with --experimental-vm-modules --experimental-wasm-modules),\n while it remains also palatable to webpack as illustrated in webpack/webpack#14313\n (where the pkg subfolder is generated with wasm-pack built with this change).\n This resolves the headache of using a wasm-pack-built package in a library that one needs to both run directly in Node and include in a webpack build.\n\n [issue/1039]: https://github.com/rustwasm/wasm-pack/issues/1039\n [pull/1061]: https://github.com/rustwasm/wasm-pack/pull/1061\n [gthb]: https://github.com/gthb\n\n - **Use new chromdriver endpoint and fix CI - [Myriad-Dreamin], [kade-robertson], [issue/1315], [issue/1390], [pull/1325], [pull/1391]**\n\n [issue/1315]: https://github.com/rustwasm/wasm-pack/issues/1315\n [issue/1390]: https://github.com/rustwasm/wasm-pack/issues/1390\n [pull/1325]: https://github.com/rustwasm/wasm-pack/pull/1325\n [pull/1391]: https://github.com/rustwasm/wasm-pack/pull/1391\n [Myriad-Dreamin]: https://github.com/Myriad-Dreamin\n [kade-robertson]: https://github.com/kade-robertson\n\n - **Add mingw support to npm package - [nathaniel-daniel], [issue/1354], [issue/1359], [pull/1363]**\n\n Fixes the NPM package's platform detection for mingw.\n\n [issue/1354]: https://github.com/rustwasm/wasm-pack/issues/1354\n [issue/1359]: https://github.com/rustwasm/wasm-pack/issues/1359\n [pull/1363]: https://github.com/rustwasm/wasm-pack/pull/1363\n [nathaniel-daniel]: https://github.com/nathaniel-daniel\n\n - **pkg-dir option for pack and publish commands - [danielronnkvist], [issue/1369], [pull/1370]**\n\n To be able to use these commands when the output directory option to the build command isn't the default pkg.\n\n [issue/1369]: https://github.com/rustwasm/wasm-pack/issues/1369\n [pull/1370]: https://github.com/rustwasm/wasm-pack/pull/1370\n [danielronnkvist]: https://github.com/danielronnkvist\n\n - **Optimize out-dir display - [ahaoboy], [issue/1395], [pull/1396]**\n\n Optimize out-dir display.\n\n from:\n\n `[INFO]: šŸ“¦ Your wasm pkg is ready to publish at /root/code/fib-wasm/fib-rs/../fib-wasm/wasm.`\n\n to:\n\n `[INFO]: šŸ“¦ Your wasm pkg is ready to publish at /root/code/fib-wasm/fib-wasm/wasm.`\n\n [issue/1395]: https://github.com/rustwasm/wasm-pack/issues/1395\n [pull/1396]: https://github.com/rustwasm/wasm-pack/pull/1396\n [ahaoboy]: https://github.com/ahaoboy\n\n- ### šŸ› ļø Maintenance\n\n - **Fix error and warnings in install script - [lucashorward], [issue/1159], [issue/1217], [issue/1283], [pull/1320]**\n\n [issue/1159]: https://github.com/rustwasm/wasm-pack/issues/1159\n [issue/1217]: https://github.com/rustwasm/wasm-pack/issues/1217\n [issue/1283]: https://github.com/rustwasm/wasm-pack/issues/1283\n [pull/1320]: https://github.com/rustwasm/wasm-pack/pull/1320\n [lucashorward]: https://github.com/lucashorward\n\n - **Bump follow-redirects from 1.14.9 to 1.15.6 in /npm - [dependabot], [pull/1375]**\n\n [pull/1375]: https://github.com/rustwasm/wasm-pack/pull/1375\n\n - **Bump rustls-webpki from 0.100.1 to 0.100.2 - [dependabot], [pull/1323]**\n\n [pull/1341]: https://github.com/rustwasm/wasm-pack/pull/1341\n\n - **Bump rustix from 0.37.20 to 0.37.25 - [dependabot], [pull/1341]**\n\n [pull/1323]: https://github.com/rustwasm/wasm-pack/pull/1323\n [dependabot]: https://github.com/apps/dependabot\n\n - **Bump rustls from 0.21.9 to 0.21.11 - [dependabot], [pull/1385]**\n\n [pull/1385]: https://github.com/rustwasm/wasm-pack/pull/1385\n [dependabot]: https://github.com/apps/dependabot\n\n - **Bump tar from 6.1.11 to 6.2.1 in /npm - [dependabot], [pull/1379]**\n\n [pull/1379]: https://github.com/rustwasm/wasm-pack/pull/1379\n [dependabot]: https://github.com/apps/dependabot\n\n- ### šŸ“– Documentation\n\n - **Fix typo in README - [Lionelf329], [pull/1368]**\n\n [pull/1268]: https://github.com/rustwasm/wasm-pack/pull/1368\n [Lionelf329]: https://github.com/Lionelf329\n\n - **Add a description of build --target deno - [puxiao], [pull/1344]**\n\n [pull/1344]: https://github.com/rustwasm/wasm-pack/pull/1344\n [puxiao]: https://github.com/puxiao\n\n - **Document deno in build target - [sigmaSd], [pull/1348]**\n\n [pull/1348]: https://github.com/rustwasm/wasm-pack/pull/1348\n [sigmaSd]: https://github.com/sigmaSd\n\n - **Fix local navigation backing one step too far in docs - [SamuSoft], [pull/1387]**\n\n [pull/1387]: https://github.com/rustwasm/wasm-pack/pull/1387\n [SamuSoft]: https://github.com/SamuSoft\n\n - **Add --target web to quick start build command - [josephrocca], [pull/1367]**\n\n [pull/1367]: https://github.com/rustwasm/wasm-pack/pull/1367\n [josephrocca]: https://github.com/josephrocca\n\n## ā˜€ļø 0.12.1\n\n- ### šŸ¤• Fixes\n\n - **Restore --version command - [lynn], [issue/1301], [pull/1305]**\n\n The --version command got lost in space in v0.12.0. It's now brought back!\n\n [issue/1301]: https://github.com/rustwasm/wasm-pack/issues/1301\n [pull/1305]: https://github.com/rustwasm/wasm-pack/pull/1305\n [lynn]: https://github.com/lynn\n\n - **Fix value parser for Option - [Myriad-Dreamin], [issue/1304], [pull/1307]**\n\n A value parser for OsString cannot parse a command line argument for Option,\n which let it failed to specify paths for pack, publish and test commands, this faulty behavior\n was introduced in v0.12.0.\n\n [issue/1304]: https://github.com/rustwasm/wasm-pack/issues/1304\n [pull/1307]: https://github.com/rustwasm/wasm-pack/pull/1307\n [Myriad-Dreamin]: https://github.com/Myriad-Dreamin\n\n## ā˜€ļø 0.12.0\n\n- ### āœØ Features\n\n - **Add --no-pack flag to build command - [hamza1311], [ashleygwilliams], [issue/691], [issue/811], [pull/695], [pull/1291]**\n\n When calling wasm-pack build a user can optionally pass --no-pack and wasm-pack will build your wasm, generate js, and not build a package.json.\n\n [issue/691]: https://github.com/rustwasm/wasm-pack/issues/691\n [issue/811]: https://github.com/rustwasm/wasm-pack/issues/811\n [pull/695]: https://github.com/rustwasm/wasm-pack/pull/695\n [pull/1291]: https://github.com/rustwasm/wasm-pack/pull/1291\n [ashleygwilliams]: https://github.com/ashleygwilliams\n\n - **Add wasmbindgen option: omit_default_module_path - [matthiasgeihs], [pull/1272]**\n\n Adds an option to call wasm-bindgen with --omit_default_module_path.\n\n [pull/1272]: https://github.com/rustwasm/wasm-pack/pull/1272\n [matthiasgeihs]: https://github.com/matthiasgeihs\n\n- ### šŸ¤• Fixes\n\n - **Add HTTP header USER-AGENT - [LeviticusNelson], [issue/1266], [pull/1285]**\n\n We encountered some issues when we didn't send an User-Agent. This is now fixed.\n\n [issue/1266]: https://github.com/rustwasm/wasm-pack/issues/1266\n [pull/1285]: https://github.com/rustwasm/wasm-pack/pull/1285\n [LeviticusNelson]: https://github.com/LeviticusNelson\n\n - **Replace curl with ureq - [hamza1311], [issue/650], [issue/823], [issue/997], [issue/1079], [issue/1203], [issue/1234], [issue/1281], [pull/1290]**\n\n The HTTP client is now pure Rust. Removes the dependency of openssl which have caused a lot of issues for people using wasm-pack on various distributions.\n\n [issue/650]: https://github.com/rustwasm/wasm-pack/issues/650\n [issue/823]: https://github.com/rustwasm/wasm-pack/issues/823\n [issue/997]: https://github.com/rustwasm/wasm-pack/issues/997\n [issue/1079]: https://github.com/rustwasm/wasm-pack/issues/1079\n [issue/1203]: https://github.com/rustwasm/wasm-pack/issues/1203\n [issue/1234]: https://github.com/rustwasm/wasm-pack/issues/1234\n [issue/1281]: https://github.com/rustwasm/wasm-pack/issues/1281\n [pull/1290]: https://github.com/rustwasm/wasm-pack/pull/1290\n [hamza1311]: https://github.com/hamza1311\n\n - **Update binary-install to 0.2.0. binary-install replaced curl with ureq - [drager]**\n\n See [PR](https://github.com/rustwasm/binary-install/pull/24) in binary-install repo for more information.\n\n [drager]: https://github.com/drager\n\n - **Remove --always-auth from npm login - [EstebanBorai], [pull/1288]**\n\n npm login doesn't support --always-auth anymore, instead it is under the adduser subcommand.\n\n [pull/1288]: https://github.com/rustwasm/wasm-pack/pull/1288\n [EstebanBorai]: https://github.com/EstebanBorai\n\n - **Turn off cargo colors during log level test - [dtolnay], [pull/1294]**\n\n [pull/1294]: https://github.com/rustwasm/wasm-pack/pull/1294\n [dtolnay]: https://github.com/dtolnay\n\n - **Fix getting the target-dir in wasm_bindgen_build - [tomasol], [issue/1278], [pull/1279]**\n\n Fixes a wasm-pack panic if --target-dir was supplied (and arguments are not sorted).\n\n [issue/1278]: https://github.com/rustwasm/wasm-pack/issues/1278\n [pull/1279]: https://github.com/rustwasm/wasm-pack/pull/1279\n [tomasol]: https://github.com/tomasol\n\n - **Respect package.readme in Cargo.toml - [heaths], [issue/1215], [pull/1298], [pull/1216]**\n\n wasm-pack now respects specifying readme=false:\n\n ```toml\n [package]\n readme = false\n ```\n\n [issue/1215]: https://github.com/rustwasm/wasm-pack/issues/1215\n [pull/1298]: https://github.com/rustwasm/wasm-pack/pull/1298\n [pull/1216]: https://github.com/rustwasm/wasm-pack/pull/1216\n [heaths]: https://github.com/heaths\n\n- ### šŸ“– Documentation\n\n - **Don't hide install options behind link - [oyamauchi], [issue/355], [pull/1242]**\n\n [issue/355]: https://github.com/rustwasm/wasm-pack/issues/355\n [pull/1242]: https://github.com/rustwasm/wasm-pack/issues/1242\n [oyamauchi]: https://github.com/oyamauchi\n\n- ### šŸ› ļø Maintenance\n\n - **Bump cargo-generate version to 0.18.2 - [sassman], [issue/1245] [pull/1269]**\n\n [issue/1245]: https://github.com/rustwasm/wasm-pack/issues/1245\n [pull/1269]: https://github.com/rustwasm/wasm-pack/pull/1269\n [sassman]: https://github.com/sassman\n\n - **Replace unmaintained actions-rs/toolchain action in CI workflows - [striezel], [pull/1246]**\n\n Now we are using https://github.com/dtolnay/rust-toolchain instead.\n\n [pull/1246]: https://github.com/rustwasm/wasm-pack/pull/1246\n [striezel]: https://github.com/striezel\n\n - **Update several dependencies - [hamza1311], [pull/1292]**\n\n Updated clap, toml, predicates and serial_test to their latest versions.\n\n [pull/1292]: https://github.com/rustwasm/wasm-pack/pull/1292\n\n## šŸŒ¦ļø 0.11.1\n\n- ### šŸ¤• Fixes\n\n - **Fix discovery of locally installed `wasm-opt` - [Liamolucko], [issue/1247], [pull/1257]**\n\n [issue/1247]: https://github.com/rustwasm/wasm-pack/issues/1247\n [pull/1257]: https://github.com/rustwasm/wasm-pack/pull/1257\n [Liamolucko]: https://github.com/Liamolucko\n\n - **Fix wasm-pack bin script entry - [ahippler], [issue/1248], [pull/1250]**\n\n [issue/1248]: https://github.com/rustwasm/wasm-pack/issues/1248\n [pull/1250]: https://github.com/rustwasm/wasm-pack/pull/1250\n [ahippler]: https://github.com/ahippler\n\n- ### šŸ› ļø Maintenance\n\n - **bump openssl from 0.10.46 to 0.10.48 - [pull/1254]**\n\n [pull/1254]: https://github.com/rustwasm/wasm-pack/pull/1254\n\n## šŸŒ¦ļø 0.11.0\n\n- ### āœØ Features\n\n - **Make Deno target available - [egfx-notifications], [issue/672], [issue/879], [pull/1117]**\n\n [issue/672]: https://github.com/rustwasm/wasm-pack/issues/672\n [issue/879]: https://github.com/rustwasm/wasm-pack/issues/879\n [pull/1117]: https://github.com/rustwasm/wasm-pack/pull/1117\n [egfx-notifications]: https://github.com/egfx-notifications\n\n - **Add support for more platforms to installer script - [omninonsense], [issue/1064], [issue/952], [issue/1125], [pull/1122]**\n\n This makes the installation script work on M1 macs, as well as inside docker (especially when combined with buildx) for aarch64/arm64 architectures.\n\n [issue/1064]: https://github.com/rustwasm/wasm-pack/issues/1064\n [issue/952]: https://github.com/rustwasm/wasm-pack/issues/952\n [issue/1125]: https://github.com/rustwasm/wasm-pack/issues/1125\n [pull/1122]: https://github.com/rustwasm/wasm-pack/pull/1122\n [omninonsense]: https://github.com/omninonsense\n\n - **Add Linux arm64 support - [nnelgxorz], [issue/1169], [pull/1170]**\n\n [issue/1169]: https://github.com/rustwasm/wasm-pack/issues/1169\n [pull/1170]: https://github.com/rustwasm/wasm-pack/pull/1170\n [nnelgxorz]: https://github.com/nnelgxorz\n\n - **Add support for workspace inheritance - [printfn], [issue/1180], [pull/1185]**\n\n [issue/1180]: https://github.com/rustwasm/wasm-pack/issues/1180\n [pull/1185]: https://github.com/rustwasm/wasm-pack/pull/1185\n\n- ### šŸ¤• Fixes\n\n - **--target-dir as extra option is now considered as expected - [sassman], [issue/1076], [pull/1082]**\n\n [issue/1076]: https://github.com/rustwasm/wasm-pack/issues/1076\n [pull/1082]: https://github.com/rustwasm/wasm-pack/pull/1082\n [sassman]: https://github.com/sassman\n\n - **Pass through --weak-refs --reference-types flags to bindgen - [serprex], [issue/930], [pull/937]**\n\n [issue/930]: https://github.com/rustwasm/wasm-pack/issues/930\n [pull/937]: https://github.com/rustwasm/wasm-pack/pull/937\n [serprex]: https://github.com/serprex\n\n - **Fix binaryen URL and use updated binary-install to fix installation on macOS - [matheus23], [printfn], [pull/1188]**\n\n Use the updated binary-install crate (rustwasm/binary-install#21), switches from failure to anyhow to match what binary-install uses, and fixes wasm-opt installation on macOS.\n\n [pull/1188]: https://github.com/rustwasm/wasm-pack/pull/1188\n [matheus23]: https://github.com/matheus23\n [printfn]: https://github.com/printfn\n [rustwasm/binary-install#21]: https://github.com/rustwasm/binary-install/pull/21\n\n - **Mark snippets and the bundler target's main file as having side effects - [Liamolucko], [issue/972], [rustwasm/wasm-bindgen/3276], [pull/1224]**\n\n [issue/972]: https://github.com/rustwasm/wasm-pack/issues/972\n [rustwasm/wasm-bindgen/3276]: https://github.com/rustwasm/wasm-bindgen/issues/3276\n [pull/1224]: https://github.com/rustwasm/wasm-pack/pull/1224\n [Liamolucko]: https://github.com/Liamolucko\n\n- ### šŸ“– Documentation\n\n - **Fix typos in non-rustup-setups.md - [dallasbrittany], [issue/1141], [pull/1142]**\n\n [issue/1141]: https://github.com/rustwasm/wasm-pack/issues/1141\n [pull/1142]: https://github.com/rustwasm/wasm-pack/issues/1141\n [dallasbrittany]: https://github.com/dallasbrittany\n\n - **Fix typos in considerations.md - [lhjt], [pull/1066]**\n\n [pull/1066]: https://github.com/rustwasm/wasm-pack/pull/1066\n [lhjt]: https://github.com/lhjt\n\n - **Grammar and typo fixes - [helixbass], [pull/1143]**\n\n [pull/1143]: https://github.com/rustwasm/wasm-pack/pull/1143\n [helixbass]: https://github.com/helixbass\n\n - **Replace two mentions of wasm-pack init with wasm-pack build in the docs - [mstange], [pull/1086]**\n\n [pull/1086]: https://github.com/rustwasm/wasm-pack/pull/1086\n [mstange]: https://github.com/mstange\n\n - **Update npm installation link - [benediktwerner], [pull/1227]**\n\n [pull/1227]: https://github.com/rustwasm/wasm-pack/pull/1227\n [benediktwerner]: https://github.com/benediktwerner\n\n- ### šŸ› ļø Maintenance\n\n - **Bump wasm-opt to version 108 - [MichaelMauderer], [issue/1135] [pull/1136]**\n\n [pull/1136]: https://github.com/rustwasm/wasm-pack/pull/1136\n [issue/1135]: https://github.com/rustwasm/wasm-pack/issues/1135\n [MichaelMauderer]: https://github.com/MichaelMauderer\n\n - **Update binary-install to v1.0.1 - [EverlastingBugstopper], [pull/1130]**\n\n [pull/1130]: https://github.com/rustwasm/wasm-pack/pull/1130\n\n - **Add back run.js to npm installer - [EverlastingBugstopper], [pull/1149]**\n\n [pull/1149]: https://github.com/rustwasm/wasm-pack/pull/1149\n\n - **Fix some typos in the codebase - [striezel], [pull/1220]**\n\n [pull/1220]: https://github.com/rustwasm/wasm-pack/pull/1220\n [striezel]: https://github.com/striezel\n\n - **Update actions/checkout in GitHub Actions workflows to v3 - [striezel], [pull/1221]**\n\n [pull/1221]: https://github.com/rustwasm/wasm-pack/pull/1221\n\n - **Update actions/cache in GitHub Actions workflows to v3 - [striezel], [pull/1222]**\n\n [pull/1222]: https://github.com/rustwasm/wasm-pack/pull/1222\n\n - **Update JamesIves/github-pages-deploy-action in GHA workflow to v4.4.1 - [striezel], [pull/1223]**\n\n [pull/1223]: https://github.com/rustwasm/wasm-pack/pull/1223\n\n## šŸŒ¦ļø 0.10.3\n\n- ### šŸ¤• Fixes\n\n - **Use bash to create release tarballs - [nasso], [issue/1097] [pull/1144]**\n\n Fixes Windows installer failure due to malformatted tar.\n\n [pull/1144]: https://github.com/rustwasm/wasm-pack/pull/1144\n [issue/1097]: https://github.com/rustwasm/wasm-pack/issues/1097\n [nasso]: https://github.com/nasso\n\n - **Clean up package.json from previous runs - [main--], [issue/1110-comment] [pull/1119]**\n\n Remove the package.json file from previous runs to avoid crashes.\n\n [pull/1119]: https://github.com/rustwasm/wasm-pack/pull/1119\n [issue/1110-comment]: https://github.com/rustwasm/wasm-pack/pull/1110#issuecomment-1059008962\n [main--]: https://github.com/main--\n\n - **Do not remove the pkg directory - [huntc], [issue/1099] [pull/1110]**\n\n A recent change ensured that the pkg directory was removed as the first step of attempting to create it.\n Unfortunately, this caused a problem for webpack when watching the pkg directory.\n Webpack was unable to recover its watching and so any watch server must be restarted,\n which is a blocker when using it. This PR and release fixes this.\n\n [pull/1110]: https://github.com/rustwasm/wasm-pack/pull/1110\n [issue/1099]: https://github.com/rustwasm/wasm-pack/issues/1099\n [huntc]: https://github.com/huntc\n\n - **Bump regex from 1.5.4 to 1.5.6 - [dependabot], [pull/1147]**\n\n Version 1.5.5 of the regex crate fixed a security bug in the regex compiler.\n\n [pull/1147]: https://github.com/rustwasm/wasm-pack/pull/1147\n\n - **Bump openssl-src from 111.17.0+1.1.1m to 111.20.0+1.1.1o - [dependabot], [pull/1146]**\n\n Bring in bug fixes from the new version of openssl-src.\n\n [pull/1146]: https://github.com/rustwasm/wasm-pack/pull/1146\n [dependabot]: https://github.com/apps/dependabot\n\n## šŸŒ¦ļø 0.10.2\n\n- ### āœØ Features\n\n - **Implement support for RFC 8, transitive NPM dependencies - [jpgneves], [issue/606] [pull/986]**\n\n [pull/986]: https://github.com/rustwasm/wasm-pack/pull/986\n [issue/606]: https://github.com/rustwasm/wasm-pack/issues/606\n [jpgneves]: https://github.com/jpgneves\n\n- ### šŸ¤• Fixes\n\n - **Add support for macos aarch64 - [d3lm], [issue/913] [pull/1088]**\n\n This fixes aarch64 for MacOS and will download x86_64-apple-darwin.\n\n [pull/1088]: https://github.com/rustwasm/wasm-pack/pull/1088\n [issue/913]: https://github.com/rustwasm/wasm-pack/issues/913\n [d3lm]: https://github.com/d3lm\n\n - **Add linux/arm64 to release workflow - [nacardin], [issue/1064] [pull/1065]**\n\n [pull/1065]: https://github.com/rustwasm/wasm-pack/pull/1065\n [issue/1064]: https://github.com/rustwasm/wasm-pack/issues/1064\n [nacardin]: https://github.com/nacardin\n\n - **Force axios version - [drager], [pull/1094]**\n\n Forces npm package `axios` to version `0.21.2` in order to get security fix for a security vulnerability present in axios\n before version `0.21.2`.\n\n [pull/1094]: https://github.com/rustwasm/wasm-pack/pull/1094\n\n- ### šŸ“– Documentation\n\n - **Update docs for how to pass extra options to cargo - [FrankenApps], [issue/1059] [pull/1073]**\n\n [FrankenApps]: https://github.com/FrankenApps\n [pull/1073]: https://github.com/rustwasm/wasm-pack/pull/1073\n [issue/1059]: https://github.com/rustwasm/wasm-pack/issues/1059\n\n## šŸŒ¦ļø 0.10.1\n\n- ### šŸ¤• Fixes\n\n - **Add exe to binary name if windows - [drager], [issue/1038] [pull/1055]**\n\n [pull/1055]: https://github.com/rustwasm/wasm-pack/pull/1055\n [issue/1038]: https://github.com/rustwasm/wasm-pack/issues/1038\n\n## šŸŒ¦ļø 0.10.0\n\n- ### āœØ Features\n\n - **Added keywords - [lucashorward], [issue/707] [pull/838]**\n\n `package.json` files usually contain a keywords array so that npm can make searching easier.\n This PR extracts keywords from `Cargo.toml` and puts them into `package.json`.\n\n [lucashorward]: https://github.com/lucashorward\n [pull/838]: https://github.com/rustwasm/wasm-pack/pull/838\n [issue/707]: https://github.com/rustwasm/wasm-pack/issues/707\n\n- ### šŸ¤• Fixes\n\n - **Update binary-install to get fix for axios security vulnerability - [simlay], [Rizary], [issue/958] [pull/973] [pull/1012]**\n\n Updates `binary-install` npm package to version `^0.1.0` in order to get security fix for a security vulnerability in axios.\n\n [simlay]: https://github.com/simlay\n [rizary]: https://github.com/Rizary\n [pull/973]: https://github.com/rustwasm/wasm-pack/pull/973\n [pull/1012]: https://github.com/rustwasm/wasm-pack/pull/1012\n [issue/958]: https://github.com/rustwasm/wasm-pack/issues/958\n\n - **Fix cargo-generate installation - [bradyjoslin], [issue/975] [issue/907] [pull/983]**\n\n `wasm-pack new hello-wasm` didn't work due to a bad link when trying to install `cargo-generate`.\n\n This PR points the installation to the correct place and makes `wasm-pack new` working again!\n\n [bradyjoslin]: https://github.com/bradyjoslin\n [pull/983]: https://github.com/rustwasm/wasm-pack/pull/983\n [issue/975]: https://github.com/rustwasm/wasm-pack/issues/975\n [issue/907]: https://github.com/rustwasm/wasm-pack/issues/907\n\n - **Pass through extra options when building tests - [azriel91], [issue/698] [pull/851]**\n\n `wasm-pack test` accepts extra options to pass through to `cargo` when running tests.\n Under the hood, this runs `cargo build` before `cargo test`, and the additional options were only passed through to the `test` command. This meant that crates that enabled native features by default could not be built using `wasm-pack`, as it would attempt to build tests for the `wasm32-unknown-unknown` target with the native features enabled.\n\n This PR passes through the extra options to `cargo` when building the tests as well.\n\n [azriel91]: https://github.com/azriel91\n [pull/851]: https://github.com/rustwasm/wasm-pack/pull/851\n [issue/698]: https://github.com/rustwasm/wasm-pack/issues/698\n\n - **Corrected files included in package.json for bundler / no target - [lucashorward], [issue/837] [pull/839]**\n\n `wasm-pack build` and `wasm-pack build --target bundler` generates a \\_bg.js file, but it was not added to the `package.json`.\n The file that is added, \\*.js will however reference the \\_bg.js, so when the package was distributed (both through pack or publish) it is not usable.\n\n This PR includes that \\_bg.js file in `package.json`.\n\n [pull/839]: https://github.com/rustwasm/wasm-pack/pull/839\n [issue/837]: https://github.com/rustwasm/wasm-pack/issues/837\n\n - **Find the main package if multiple packages have the same name - [ghost], [pull/830]**\n\n If there were 2 packages with the same name, `wasm-pack` would sometimes use the wrong one and errored.\n\n [ghost]: https://github.com/ghost\n [pull/830]: https://github.com/rustwasm/wasm-pack/pull/830\n [issue/829]: https://github.com/rustwasm/wasm-pack/issues/829\n\n- ### šŸ“– Documentation\n\n - **Remove duplicated \"is\" in the wee_alloc tutorial- [pione30], [issue/1003] [pull/1004]**\n\n [pione30]: https://github.com/pione30\n [pull/1004]: https://github.com/rustwasm/wasm-pack/pull/1004\n [issue/1003]: https://github.com/rustwasm/wasm-pack/issues/1003\n\n - **Fix TOC links - [Swaagie], [pull/1007]**\n\n [swaagie]: https://github.com/Swaagie\n [pull/1007]: https://github.com/rustwasm/wasm-pack/pull/1007\n\n - **Remove outdated TOC heading- [gthb], [pull/1011]**\n\n [gthb]: https://github.com/gthb\n [pull/1011]: https://github.com/rustwasm/wasm-pack/pull/1011\n\n - **Add link to template repo - [milahu], [pull/942]**\n\n [milahu]: https://github.com/milahu\n [pull/942]: https://github.com/rustwasm/wasm-pack/pull/942\n\n - **Remove greenkeeper reference - [cdvv7788], [crotwell], [issue/1001] [pull/844] [pull/1002]**\n\n [cdvv7788]: https://github.com/cdvv7788\n [crotwell]: https://github.com/crotwell\n [pull/844]: https://github.com/rustwasm/wasm-pack/pull/844\n [pull/1002]: https://github.com/rustwasm/wasm-pack/pull/1002\n [issue/1001]: https://github.com/rustwasm/wasm-pack/issues/1001\n\n- ### šŸ› ļø Maintenance\n\n - **Fix CI. Remove appveyor and travis and use Github actions - [ashleygwilliams], [drager], [issue/594] [issue/979] [pull/947]**\n\n [pull/947]: https://github.com/rustwasm/wasm-pack/pull/947\n [issue/594]: https://github.com/rustwasm/wasm-pack/issues/594\n [issue/979]: https://github.com/rustwasm/wasm-pack/issues/979\n\n - **Cargo update - [ashleygwilliams], [pull/800]**\n\n [ashleygwilliams]: https://github.com/ashleygwilliams\n [pull/800]: https://github.com/rustwasm/wasm-pack/pull/800\n\n - **Remove dirs dependency - [brightly-salty], [issue/943] [pull/944]**\n\n [brightly-salty]: https://github.com/brightly-salty\n [pull/944]: https://github.com/rustwasm/wasm-pack/pull/944\n [issue/943]: https://github.com/rustwasm/wasm-pack/issues/943\n\n - **Fix logs for uniformity - [petosorus], [issue/716] [pull/723]**\n\n [petosorus]: https://github.com/petosorus\n [pull/723]: https://github.com/rustwasm/wasm-pack/pull/723\n [issue/716]: https://github.com/rustwasm/wasm-pack/issues/716\n\n - **Fixing build error - [Pauan], [pull/841]**\n\n [pull/841]: https://github.com/rustwasm/wasm-pack/pull/841\n\n## ā˜ļø 0.9.1\n\n- ### šŸ¤• Fixes\n\n - **Bump binaryen to version_90 - [ashleygwilliams], [issue/781] [issue/782] [pull/687]**\n\n Previously, wasm-pack was hardcoded to install and attempt to execute wasm-opt on every build\n using binaryen version 78. This version had various issues on Unix/Linux and caused broken CI\n builds for many folks (we're so sorry!).\n\n This PR updates the binaryen version to 90, which should fix the issues folks were having.\n\n Long-term, we'd like to create an auto-updating mechanism so that we can install and use the\n latest release of binaryen as we do for other binaries we orchestrate.\n\n [ashleygwilliams]: https://github.com/ashleygwilliams\n [pull/687]: https://github.com/rustwasm/wasm-pack/pull/687\n [issue/782]: https://github.com/rustwasm/wasm-pack/issues/782\n [issue/781]: https://github.com/rustwasm/wasm-pack/issues/781\n\n- ### šŸ› ļø Maintenance\n\n - **Consolidate wasm-opt installation into existing binary install logic - [ashleygwilliams], [issue/685] [pull/687]**\n\n [ashleygwilliams]: https://github.com/ashleygwilliams\n [pull/687]: https://github.com/rustwasm/wasm-pack/pull/687\n [issue/685]: https://github.com/rustwasm/wasm-pack/issues/685\n\n## šŸŒ„ļø 0.9.0\n\n- ### āœØ Features\n\n - **Adding in `--quiet` and `--log-level` flags to control the console output - [Pauan], [pull/694]**\n\n The `--verbose` flag has long existed as a way to get more console output, but now there are two flags to get _less_ console output:\n\n - `--quiet` will silence _all_ stdout, so only errors will be displayed.\n - `--log-level` can be used to silence `[INFO]` or `[WARN]` output from wasm-pack.\n\n You can cause it to display even _more_ information by using `--verbose`, or you can silence _all_ stdout by using `--quiet`.\n\n You can also use `--log-level` to have fine-grained control over wasm-pack's log output:\n\n - `--log-level info` is the default, it causes all messages to be logged.\n - `--log-level warn` causes warnings and errors to be displayed, but not info.\n - `--log-level error` causes only errors to be displayed.\n\n These flags are global flags, so they can be used with every command, and they must come _before_ the command:\n\n ```sh\n wasm-pack --log-level error build\n wasm-pack --quiet build\n ```\n\n [Pauan]: https://github.com/Pauan\n [pull/694]: https://github.com/rustwasm/wasm-pack/pull/694\n\n - **Wrap `cargo-generate` with `wasm-pack new` - [ashleygwilliams], [issue/373] [pull/623]**\n\n One of the first steps in getting started with `wasm-pack` is to `cargo install cargo-generate` to bootstrap some project templates. This can take a while and is an extra burden on users just getting started with `wasm-pack`. `wasm-pack new` uses `cargo-generate` to bootstrap new projects, removing the need to install the tool on your own. You can read more about this feature [here](https://github.com/rustwasm/wasm-pack/blob/master/docs/src/commands/new.md).\n\n [ashleygwilliams]: https://github.com/ashleygwilliams\n [pull/623]: https://github.com/rustwasm/wasm-pack/pull/623\n [issue/373]: https://github.com/rustwasm/wasm-pack/issues/373\n\n - **Allow `wasm-pack` to be run from subdirectories - [gameldar], [issue/620] [pull/624]**\n\n If a crate path is not specified when running `wasm-pack` and there is no `Cargo.toml` in the current working directory, `wasm-pack` will walk up the directory structure to find a `Cargo.toml`.\n\n [gameldar]: https://github.com/gameldar\n [pull/624]: https://github.com/rustwasm/wasm-pack/pull/624\n [issue/620]: https://github.com/rustwasm/wasm-pack/issues/620\n\n - **Automatically execute `wasm-opt` on produced binaries - [alexcrichton], [issue/159] [pull/625]**\n\n When `wasm-pack` builds binaries in released and profiling modes, it will execute `wasm-opt` on the binary, making the result smaller and more performant.\n\n [alexcrichton]: https://github.com/alexcrichton\n [pull/625]: https://github.com/rustwasm/wasm-pack/pull/625\n [issue/159]: https://github.com/rustwasm/wasm-pack/issues/159\n\n - **Helpful error message when wasm-bindgen fails because of an old version - [gameldar], [ashleygwilliams], [issue/627] [pull/633]**\n\n `wasm-pack` will pass a `--web` flag to `wasm-bindgen` when `wasm-pack build --target web` is run. Before, if the user had an old version of `wasm-bindgen` in their dependencies, they would receive a cryptic error message. Now they will be notified that they need to update their `wasm-bindgen` dependency if they want to build for the `web` target.\n\n [gameldar]: https://github.com/gameldar\n [pull/633]: https://github.com/rustwasm/wasm-pack/pull/633\n [issue/627]: https://github.com/rustwasm/wasm-pack/issues/627\n\n - **Publish releases by tag to npm - [Tarnadas], [pull/690]**\n\n You can now use `wasm-pack publish` to publish tagged releases with the optional `--tag` argument. You can read more about [distribution tags](https://docs.npmjs.com/cli/dist-tag) on NPM, and more about this feature in [our docs](https://github.com/Tarnadas/wasm-pack/blob/master/docs/src/commands/pack-and-publish.md#publishing-tagged-releases).\n\n [Tarnadas]: https://github.com/Tarnadas\n [pull/690]: https://github.com/rustwasm/wasm-pack/pull/690\n\n- ### šŸ¤• Fixes\n\n - **Only use exactly v0.24.0 geckodriver on Windows - [ashleygwilliams], [issue/770] [pull/774]**\n\n `wasm-pack test` is a great way to test your web Wasm modules- and it very nicely sets up and configures\n the necessary browser engine drivers to do so!\n\n For the v0.25.0 release of geckodriver, the team switched their build environment- which introduced a new\n surprise runtime dependency, Visual C++ redistributable package, to their windows binaries. You can read\n more about the issue here, [mozilla/geckodriver/issue/1617].\n\n Becuase the introduction of this runtime dependency is considered a bug, and should be eventually fixed,\n the team decided that the least invasive solution would be to hold geckodriver binaries, on Windows, at\n v0.24.0, and to disable the auto-update logic, until the bug is fixed.\n\n [ashleygwilliams]: https://github.com/ashleygwilliams\n [issue/770]: https://github.com/rustwasm/wasm-pack/issues/770\n [pull/774]: https://github.com/rustwasm/wasm-pack/pull/774\n [mozilla/geckodriver/issue/1617]: https://github.com/mozilla/geckodriver/issues/1617#issuecomment-532168958\n\n - **Handle version check failures - [drager], [issue/652], [issue/653] [pull/660]**\n\n Every day, `wasm-pack` checks the crates.io API for the latest version number and lets the user know if their installation is out of date. Now, when these API calls fail, `wasm-pack` alerts the user of the failure and waits until the next day to make another call to crates.io.\n\n [drager]: https://github.com/drager\n [pull/660]: https://github.com/rustwasm/wasm-pack/pull/660\n [issue/652]: https://github.com/rustwasm/wasm-pack/issues/652\n [issue/653]: https://github.com/rustwasm/wasm-pack/issues/653\n\n - **Add user agent for version check - [drager], [issue/651] [pull/658]**\n\n crates.io requires tools to set a version check `User-Agent` header when requesting the latest version. Now, when `wasm-pack` performs an API request to crates.io, it sends `User-Agent: wasm-pack/0.9.0`.\n\n [drager]: https://github.com/drager\n [pull/658]: https://github.com/rustwasm/wasm-pack/pull/658\n [issue/651]: https://github.com/rustwasm/wasm-pack/issues/651\n\n - **Remove broken link from the README - [drager], [pull/635]**\n\n [drager]: https://github.com/drager\n [pull/635]: https://github.com/rustwasm/wasm-pack/pull/635\n\n - **Make `sideEffects` in generated `package.json` a boolean instead of a string - [rhysd], [pull/649]**\n\n [rhysd]: https://github.com/rhysd\n [pull/649]: https://github.com/rustwasm/wasm-pack/pull/649\n\n - **Don't warn if license-file is present - [ashleygwilliams], [issue/692] [pull/693]**\n\n Previously, `wasm-pack` would warn that the `license` field was missing if the `license-file` field was used instead. This warning is now only surfaced if both `license` and `license-field` are absent from a `Cargo.toml`.\n\n [ashleygwilliams]: https://github.com/ashleygwilliams\n [pull/693]: https://github.com/rustwasm/wasm-pack/pull/693\n [issue/692]: https://github.com/rustwasm/wasm-pack/issues/692\n\n - **Select correct webdriver version - [MartinKavik], [issue/611] [pull/706]**\n\n `wasm-pack` used to install a pinned version of the Chrome, Gecko, and Safari drivers. Now when a driver needs to be installed, `wasm-pack` will pull the latest version from the API and install that instead.\n\n [MartinKavik]: https://github.com/MartinKavik\n [pull/706]: https://github.com/rustwasm/wasm-pack/pull/706\n [issue/611]: https://github.com/rustwasm/wasm-pack/issues/611\n\n - **Only run node tests on `wasm-pack test --node` - [alexcrichton], [pull/630]**\n\n [alexcrichton]: https://github.com/alexcrichton\n [pull/630]: https://github.com/rustwasm/wasm-pack/pull/630\n\n - **Fix npm installs for Windows Users - [EverlastingBugstopper], [issue/757] [pull/759]**\n\n We recently published `wasm-pack` on the npm registry but forgot to test on Windows! `npm install -g wasm-pack` now works on Windows machines.\n\n [EverlastingBugstopper]: https://github.com/EverlastingBugstopper\n [pull/759]: https://github.com/rustwasm/wasm-pack/pull/759\n [issue/757]: https://github.com/rustwasm/wasm-pack/issues/757\n\n - **Clean up `cargo test` warnings - [ashleygwilliams], [issue/752] [pull/753]**\n\n Tests now use `std::sync::Once::new()` instead of the deprecated `std::sync::ONCE_INIT`\n\n [ashleygwilliams]: https://github.com/ashleygwilliams\n [pull/753]: https://github.com/rustwasm/wasm-pack/pull/753\n [issue/752]: https://github.com/rustwasm/wasm-pack/issues/752\n\n- ### šŸ“– Documentation\n\n - **Document npm installer - [drager], [issue/751] [pull/767]**\n\n [drager]: https://github.com/drager\n [issue/751]: https://github.com/rustwasm/wasm-pack/issues/751\n [pull/767]: https://github.com/rustwasm/wasm-pack/pull/767\n\n - **Update help message for `build` and `publish` subcommands - [ibaryshnikov], [issue/636] [pull/640]**\n\n `wasm-bindgen` recently changed the default target from `browser` to `bundler` and deprecated `browser`. This change is now reflected in the help message for `wasm-pack build`.\n\n [ibaryshnikov]: https://github.com/ibaryshnikov\n [pull/640]: https://github.com/rustwasm/wasm-pack/pull/640\n [issue/636]: https://github.com/rustwasm/wasm-pack/issues/636\n\n - **Add Release Checklist - [ashleygwilliams], [issue/370] [pull/626]**\n\n While we try to automate releases of `wasm-pack` as much as possible, there are still some manual steps that need to be completed when releasing a new version (like writing a changelog šŸ˜‰). These steps now live in [`RELEASE_CHECKLIST.md`](https://github.com/rustwasm/wasm-pack/blob/master/RELEASE_CHECKLIST.md).\n\n [ashleygwilliams]: https://github.com/ashleygwilliams\n [pull/626]: https://github.com/rustwasm/wasm-pack/pull/626\n [issue/370]: https://github.com/rustwasm/wasm-pack/issues/370\n\n- ### šŸ› ļø Maintenance\n\n - **Ensure that `wasm-bindgen` generates move assertions - [fitzgen], [issue/677] [pull/683]**\n\n `wasm-pack` now creates `wasm-bindgen` test fixtures that must generate move assertions for both free functions and methods.\n\n [fitzgen]: https://github.com/fitzgen\n [pull/683]: https://github.com/rustwasm/wasm-pack/pull/683\n [issue/677]: https://github.com/rustwasm/wasm-pack/issues/677\n\n - **Update `cargo_metadata` to v0.8.0 - [ThomasdenH], [pull/670]**\n\n [ThomasdenH]: https://github.com/ThomasdenH\n [pull/670]: https://github.com/rustwasm/wasm-pack/pull/670\n\n - **Update `rustfmt` install snippet in PR template` - [data-pup], [issue/639] [pull/664]**\n\n `rustfmt` is now available on Rust's stable channel so now the `wasm-pack` PR template recommends installing the stable version instead of the nightly version.\n\n [data-pup]: https://github.com/data-pup\n [pull/664]: https://github.com/rustwasm/wasm-pack/pull/664\n [issue/639]: https://github.com/rustwasm/wasm-pack/issues/639\n\n## šŸ› ļø 0.8.1\n\n- ### šŸ¤• Fixes\n\n - **Check for \"rustup\" rather than \".rustup\" when checking for wasm32 - [drager], [issue/613][pull/616]**\n\n When we introduced support for non-rustup setups we did a check if the user was\n using rustup or not. However, this check was too constrained and only covered\n the most common cases, but it did not work for Docker setups.\n\n This PR addresses that and it now covers Docker setups as well!\n When doing this fix we also found two other small issues which this PR also addresses.\n The first is that we did not print the helpful error message when the wasm32 target\n was not found and the other one was that it linked to the wrong section of the documentation.\n\n [issue/613]: https://github.com/rustwasm/wasm-pack/issues/613\n [pull/616]: https://github.com/rustwasm/wasm-pack/pull/616\n\n## šŸŒ¤ļø 0.8.0\n\n- ### āœØ Features\n\n - **Give user's ability to customize generated filenames with `--out-name` flag - [ibaryshnikov], [issue/596] [pull/599]**\n\n When running `wasm-pack build`, several files are generated. These files\n are named based on the name of the crate, as per your `Cargo.toml` file.\n Sometimes- that's not the name you'd like your files to have!\n\n You can now specify a custom name for the generated files using a new\n flag, `--out-name`. Given a project called `dom`, here's a comparison of\n the default and custom generated filenames:\n\n ```\n wasm-pack build\n # will produce files\n # dom.d.ts dom.js dom_bg.d.ts dom_bg.wasm package.json README.md\n\n wasm-pack build --out-name index\n # will produce files\n # index.d.ts index.js index_bg.d.ts index_bg.wasm package.json README.md\n ```\n\n [ibaryshnikov]: https://github.com/ibaryshnikov\n [issue/596]: https://github.com/rustwasm/wasm-pack/issues/596\n [pull/599]: https://github.com/rustwasm/wasm-pack/pull/599\n\n- ### šŸ¤• Fixes\n\n - **Fix panics in `build mode --no-install` - [alexcrichton], [pull/598]**\n\n This commit fixes the `wasm-pack build --mode no-install` command from\n unconditionally panicking as well as `--mode force`. These steps were\n calling an `unwrap()` on an internal `Option` which was supposed to\n be set during `step_install_wasm_bindgen`, but that step wasn't run in\n these modes. The mode configuration of steps has been refactored\n slightly to ensure that more steps are shared between these modes to\n reduce duplication.\n\n [pull/598]: https://github.com/rustwasm/wasm-pack/pull/598\n\n - **Print unexpected panics to standard error - [drager], [issue/562] [pull/601]**\n\n Unexpected panics are unfortunate but they're currently covered up and written\n out to an auxiliary file. This makes panics in CI difficult to debug,\n especially at a glance, as CI builders are likely not uploading those files.\n\n This PR will print to standard error for unexpected panics and then let\n `human_panic` handle panics, just like before.\n\n [issue/562]: https://github.com/rustwasm/wasm-pack/issues/562\n [pull/601]: https://github.com/rustwasm/wasm-pack/pull/601\n\n - **Improve error message when `wasm32-unknown-unknown` is missing - [drager], [issue/579] [pull/602]**\n\n For folks with non-rustup environments (which we only started supporting in\n 0.7.0!), we were giving a missing target error that was not helpful!\n\n We've updated the error message to include more information, and we've added\n some documentation to help explain how you can remedy the error by manually\n installing the target on your specific rust setup- including the fact that\n it may _not_ be possible to add the target to some setups.\n\n Check out the docs [here](https://drager.github.io/wasm-pack/book/prerequisites/non-rustup-setups.html).\n\n [issue/579]: https://github.com/rustwasm/wasm-pack/issues/579\n [pull/602]: https://github.com/rustwasm/wasm-pack/pull/602\n\n- ### šŸ“– Documentation\n\n - **Document `--out-dir` flag - [ashleygwilliams], [issue/592] [pull/593]**\n\n Recently, someone asked on Discord about customizing the name of the directory\n that contains the assets built by `wasm-pack`. We've had the `out-dir` flag for\n a while, but it wasn't documented! Now it is.\n\n [issue/592]: https://github.com/rustwasm/wasm-pack/issues/592\n [pull/593]: https://github.com/rustwasm/wasm-pack/pull/593\n\n - **Fix broken links in docs and update for template changes - [drager], [ashleygwilliams], [issue/609] [pull/612] [pull/614]**\n\n Recently, some improvements were made to the [`wasmpack-template`]. Additionally,\n there were some broken links in the documentation. We've updated the docs for the\n new template and fixed the broken links!\n\n [issue/609]: https://github.com/rustwasm/wasm-pack/issues/609\n [pull/612]: https://github.com/rustwasm/wasm-pack/pull/612\n [pull/614]: https://github.com/rustwasm/wasm-pack/pull/614\n\n- ### šŸ› ļø Maintenance\n\n - **Move `binary-install` to its own repo - [drager], [issue/500] [pull/600]**\n\n `binary-install` is a crate that holds the abstractions for how `wasm-pack` downloads\n and caches pre-built binaries for the tools it wraps. It was originally part of the\n `wasm-pack` code, then moved into a workspace as an independent crate. Now that we\n believe it's stable, we've moved it into its own [repo](https://github.com/rustwasm/binary-install)!\n\n [issue/500]: https://github.com/rustwasm/wasm-pack/issues/500\n [pull/600]: https://github.com/rustwasm/wasm-pack/pull/600\n\n## šŸŒ¤ļø 0.7.0\n\n- ### āœØ Features\n\n - **Non `rustup` environment support - [drager], [pull/552]**\n\n Before now, `wasm-pack` had a hard requirement that `rustup` had to be in the PATH. While most Rust users use\n `rustup` there are variety reasons to have an environment that doesn't use `rustup`. With this PR, we'll now\n support folks who are using a non-`rustup` environment!\n\n [pull/552]: https://github.com/rustwasm/wasm-pack/pull/552\n\n - **Improved CLI Output - [alexcrichton], [pull/547]**\n\n It's hard to decide if this is a fix or a feature, but let's keep it positive! This PR moves `wasm-pack`'s CLI\n output strategy closer to the desired standard we have for 1.0. This is important as it fixes many small bugs\n that are distributed across a diveristy of terminals and difficult to test for locally.\n\n This strategy was first introduced as a mini RFC in [issue/298], and then was discussed in a session at the Rust\n All Hands ([notes](https://gist.github.com/fitzgen/23a62ebbd67574b9f6f72e5ac8eaeb67#file-road-to-wasm-pack-1-0-md)).\n\n You'll notice that the spinner is gone- we eventually want to have one, but we'd like one that doesn't cause bugs!\n If you have feedback about terminal support or an output bug, please [file an issue]! We want to hear from you!\n\n Check out the new output in the `README` demo- or update your `wasm-pack` and take it for a spin!\n\n [file an issue]: https://github.com/rustwasm/wasm-pack/issues/new/choose\n [pull/547]: https://github.com/rustwasm/wasm-pack/pull/547\n [issue/298]: https://github.com/rustwasm/wasm-pack/issues/298\n\n - **Add support for `--target web` - [alexcrichton], [pull/567]**\n\n Recently, `wasm-bindgen` add a new target- `web`. This new target is similar to the `no-modules` target, in that\n it is designed to generate code that should be loaded directly in a browser, without the need of a bundler. As\n opposed to the `no-modules` target, which produces an IIFE (Immediately Invoked Function Expression), this target\n produces code that is an ES6 module.\n\n You can use this target by running:\n\n ```\n wasm-pack build --target web\n ```\n\n Learn more about how to use this target by [checking out the docs!](https://drager.github.io/wasm-pack/book/commands/build.html#target)\n\n [pull/567]: https://github.com/rustwasm/wasm-pack/pull/567\n\n - **Support passing arbitrary arguments to `cargo test` via `wasm-pack test` - [chinedufn], [issue/525] [pull/530]**\n\n `wasm-pack test` is an awesome command that wraps `cargo test` in a way that helps provide you some nice out of the\n box configuration and setup. However, you may find yourself wanting to leverage the full funcationality of `cargo test`\n by passing arguments that haven't been re-exported by the `wasm-pack test` interface.\n\n For example, if you have a large test suite, it can be nice to simply run one test, or a subset of your tests.\n `cargo test` supports this, however up until now, the `wasm-pack test` interface did not!\n\n `wasm-pack test` now accepts passing and arbitrary set of arguments that it will forward along to its `cargo test` call\n by allowing users to use `--` after any `wasm-pack test` arguments, followed by the set of arguments you'd like to pass\n to `cargo test`.\n\n For example:\n\n ```\n # Anything after `--` gets passed to the `cargo test`\n wasm-pack test --firefox --headless -- --package my-workspace-crate my_test_name --color=always\n ```\n\n This will just run the `my_test_name` test and will output using color!\n\n [See the `test` docs here!](https://rustwasm.github.io/docs/wasm-pack/commands/test.html)\n\n [chinedufn]: https://github.com/chinedufn\n [issue/525]: https://github.com/rustwasm/wasm-pack/issues/525\n [pull/530]: https://github.com/rustwasm/wasm-pack/pull/530\n\n - **Support `homepage` field of `Cargo.toml` and `package.json` - [rhysd], [pull/531]**\n\n Both `Cargo.toml` and `package.json` support a `homepage` field that allow you to specify a website for\n your project. We didn't support it previously (purely an accidental omission) - but now we do!\n\n [pull/531]: https://github.com/rustwasm/wasm-pack/pull/531\n\n - **Support `license-file` field in `Cargo.toml` - [rhysd], [pull/527]**\n\n Sometimes, you want to provide a custom license, or specific license file that doesn't map to SPDX standard\n licenses. In Rust/Cargo, you accomplish this by omitting the `license` field and including a `license-file`\n field instead. You can read more about this in the [`cargo` manifest documentation].\n\n In an npm package, this translates to `\"license\": \"SEE LICENSE IN \"` in your `package.json`. You can\n read more about this in the [npm `package.json` documentation].\n\n We previously only supported using SPDX standard licenses, by only supporting the `\"license\"` key in your\n `Cargo.toml`- but now we'll allow you to leverage the `license-file` key as well, and will translate it\n correctly into your `package.json`!\n\n [`cargo` manifest documentation]: https://doc.rust-lang.org/cargo/reference/manifest.html\n [npm `package.json` documentation]: https://docs.npmjs.com/files/package.json#license\n [rhysd]: https://github.com/rhysd\n [pull/527]: https://github.com/rustwasm/wasm-pack/pull/527\n\n- ### šŸ¤• Fixes\n\n - **`wasm-pack-init (1).exe` should work - [ashleygwilliams], [issue/518] [pull/550]**\n\n Several users noted that when downloading a new version of `wasm-pack` their browser named the executable\n file `wasm-pack-init (1).exe`. When named this way, the file didn't show the init instructions on execution.\n This happened because the installation logic was requiring an exact match on filename. We've loosened that\n restriction so that the filename must _start_ with `wasm-pack-init` and will still execute files with these\n additional, extraneous charaters in the filename. Thanks so much to [Mblkolo] and [danwilhelm] for filing the\n issue and the excellent discussion!\n\n [issue/518]: https://github.com/rustwasm/wasm-pack/issues/518\n [pull/550]: https://github.com/rustwasm/wasm-pack/pull/550\n [Mblkolo]: https://github.com/Mblkolo\n\n - **Fix chromedriver error and message on Windows for `wasm-pack test` - [jscheffner], [issue/535] [pull/537]**\n\n When running `wasm-pack test` on a 64-bit Windows machine, users would receive an error:\n `geckodriver binaries are unavailable for this target`. This error message had two issues- firstly, it accidentally\n said \"geckodriver\" instead of \"chromedriver\", secondly, it threw an error instead of using the available 32-bit\n chromedriver distribution. Chromedriver does not do a specific disribution for Windows 64-bit!\n\n We've fixed the error message and have also ensured that 64-bit Windows users won't encounter an error, and will\n appropriately fallback to the 32-bit Windows chromedriver.\n\n [jscheffner]: https://github.com/jscheffner\n [issue/535]: https://github.com/rustwasm/wasm-pack/issues/535\n [pull/537]: https://github.com/rustwasm/wasm-pack/pull/537\n\n - **Correct look up location for `wasm-bindgen` when it's installed via `cargo install` - [fitzgen], [pull/504]**\n\n Sometimes, when a `wasm-bindgen` binary is not available, or if `wasm-pack` is being run on an architecture that\n `wasm-bindgen` doesn't produce binaries for, instead of downloading a pre-built binary, `wasm-pack` will install\n `wasm-bindgen` using `cargo install`. This is a great and flexible back up!\n\n However, due to the last release's recent refactor to use a global cache, we overlooked the `cargo install` case\n and did not look for `wasm-bindgen` in the appropriate location. As a result, this led to a bug where `wasm-pack`\n would panic.\n\n We've fixed the lookup for the `cargo install`'d `wasm-bindgen` by moving the `cargo-install`'d version to global\n cache location for `wasm-pack` once it's successfully built. We also eliminated the panic in favor of\n propagating an error. Thanks for your bug reports and sorry about the mistake!\n\n [pull/504]: https://github.com/rustwasm/wasm-pack/pull/504\n\n - **Only print `cargo test` output the once - [fitzgen], [issue/511] [pull/521]**\n\n Due to some technical debt and churn in the part of the codebase that handles output, we were accidentally\n printing the output of `cargo test` twice. Now we ensure that we print it only one time!\n\n [issue/511]: https://github.com/rustwasm/wasm-pack/issues/511\n [pull/521]: https://github.com/rustwasm/wasm-pack/pull/521\n\n- ### šŸ› ļø Maintenance\n\n - **Fix `clippy` warnings - [mstallmo], [issue/477] [pull/478]**\n\n [`clippy`] is an awesome utilty that helps lint your Rust code for common optimizations and idioms. at the\n beginning of `wasm-pack` development, `clippy` had not yet stablized, but it has since 1.0'd and it was\n high time we leveraged it in `wasm-pack`. We still aren't _completely_ fixed, but we're working on it, and\n we've already dervived a ton of value from the tool!\n\n [`clippy`]: https://github.com/rust-lang/rust-clippy\n [issue/477]: https://github.com/rustwasm/wasm-pack/issues/477\n [pull/478]: https://github.com/rustwasm/wasm-pack/pull/478\n\n - **Run `clippy` check on Travis - [drager], [pull/502]**\n\n Now that `wasm-pack` has been clippified- we want to keep it that way! Now in addition to `cargo fmt` and\n `cargo test`, we'll also run `cargo clippy` on all incoming PRs!\n\n [pull/502]: https://github.com/rustwasm/wasm-pack/pull/502\n\n - **Port tests to use `assert-cmd` - [fitzgen], [pull/522]**\n\n [`assert_cmd`] is a great utility for testing CLI applications that is supported by the [CLI WG]. `wasm-pack`\n development began before this library existed- so we were using a much less pleasant and efficient strategy\n to test the CLI functionality of `wasm-pack`. Now we've ported over to using this great library!\n\n [CLI WG]: https://www.rust-lang.org/what/cli\n [`assert_cmd`]: https://crates.io/crates/assert_cmd\n [pull/522]: https://github.com/rustwasm/wasm-pack/pull/522\n\n - **Add initial tests for `binary-install` crate - [drager], [pull/517]**\n\n In the last release, we separated some of our binary install logic into a new crate, `binary-install`.\n However, that's about all we did... move the logic! In an effort to move the crate into true open source\n status, [drager] has done some excellent work adding tests to the crate. This was trickier than it looked\n and involved creating a test server! Thanks for all the efforts [drager], and the great review work [fitzgen]\n and [lfairy]!\n\n [pull/517]: https://github.com/rustwasm/wasm-pack/pull/517\n [lfairy]: https://github.com/lfairy\n\n - **Update tests `wasm-bindgen` version - [huangjj27], [issue/519] [issue/417] [pull/526]**\n\n Our tests use fixtures that reference `wasm-bindgen` often, but the versions were not consistent or up to\n date. As a result, the test suite leverage many version of `wasm-bindgen` which meant that they took a while\n to run as they couldn't use the cached version of `wasm-bindgen` because the cached versions we slightly\n different! Now they are up to date and consistent so the tests can perform better!\n\n [pull/526]: https://github.com/rustwasm/wasm-pack/pull/526\n [issue/519]: https://github.com/rustwasm/wasm-pack/issues/519\n [issue/417]: https://github.com/rustwasm/wasm-pack/issues/417\n\n- ### šŸ“– Documentation\n\n - **Flag gh-pages docs as unpublished - [alexcrichton] [pull/565]**\n\n Recently, [DebugSteven] made a PR to merge all the documentation for the rustwasm toolchain into a\n [single location]. This is going to make discovering and using tools from the entire organization easier\n for new and seasoned folks alike. This also has the feature of displaying documentation that is related\n to the current published version of each tool- unlike before, where the only accessible documentation was\n for the tools at current master (which may or may not be currently published!)\n\n If you like reading the current master's documentation- fear not, each tool will still publish the\n documentation generated from the master branch on their individual `gh-pages`\n ([See `wasm-pack's` master docs here]). To avoid confusion, we've added a flash message that let's you know\n which documentation you are reading- and provides a link to documentation of the published version- just\n in case that's what you're looking for!\n\n [DebugSteve]: https://github.com/DebugSteven\n [single location]: https://rustwasm.github.io/docs.html\n [See `wasm-pack's` master docs here]: https://drager.github.io/wasm-pack/book/\n [pull/565]: https://github.com/rustwasm/wasm-pack/pull/565\n\n - **Add new QuickStart guide for \"Hybrid Applications with Webpack\" - [DebugSteven] [pull/536]**\n\n Since `wasm-pack` was first published, we've focused on a workflow where a user writes a library and then\n publishes it to npm, where anyone can use it like any npm package in their JavaScript or Node.js application.\n\n Shortly after `wasm-pack` appeared, some RustWASM teammates created a template for a similar workflow- building\n a RustWASM package _alongside_ an application. They did this by leveraging Webpack plugins, and it's a really\n lovely user experience!\n\n [This template] hasn't gotten as much attention because we've lacked a quickstart guide for folks to discover\n and follow- now we've got one!\n\n Check out the guide [here](https://drager.github.io/wasm-pack/book/tutorials/hybrid-applications-with-webpack/index.html)!\n\n [This temaplte]: https://github.com/rustwasm/rust-webpack-template\n [DebugSteven]: https://github.com/DebugSteven\n [pull/536]: https://github.com/rustwasm/wasm-pack/pull/536\n\n - **Add `wee_alloc` deepdive - [surma], [pull/542]**\n\n `wee_alloc` is a useful utility that deserved more attention and explanation than our previous docs addressed.\n This was partially because the `wasm-pack` template has an explanatory comment that helps explain its use.\n However, for folks who don't use the template, `wee_alloc` is something important to know about- so now we have\n given it its own section!\n\n Check out the deepdive [here](https://drager.github.io/wasm-pack/book/tutorials/npm-browser-packages/template-deep-dive/wee_alloc.html)!\n\n [surma]: https://github.com/surma\n [pull/542]: https://github.com/rustwasm/wasm-pack/pull/542\n\n - **Update prerequisite documentation - [alexcrichton], [pull/569]**\n\n Many folks are using `wasm-pack` without publishing to npm- as a result, we've updated the documentation to\n clearly indicate that npm is an optional requirement, only required for specific targets and workflows.\n Additionally, since the 2018 Edition landed, `nightly` Rust is no longer a requirement. We've removed those\n instructions and have consolidated the documentation so it is shorter and more efficient at getting you\n started!\n\n [pull/569]: https://github.com/rustwasm/wasm-pack/pull/569\n\n - **Clarify what kind of account `login` adds - [killercup], [pull/539]**\n\n Previously, when view `--help`, the command description for `login` showed:\n `šŸ‘¤ Add a registry user account!` This could be confusing for folks, so now it's been updated to read:\n `šŸ‘¤ Add an npm registry user account!`, which is much clearer!\n\n [killercup]: https://github.com/killercup\n [pull/539]: https://github.com/rustwasm/wasm-pack/pull/539\n\n - **Wasm is a contraction, not an acronym - [fitzgen], [pull/555]**\n\n Ever wonder how you're _actually_ supposed to refer to WebAssembly in short-form? WASM? wasm? For the pedants\n out there, the correct usage is \"Wasm\" because Wasm is a _contraction_ of the words Web and Assembly. We've\n updated our doucmentation to consistently refer to WebAssembly as Wasm in the shortform.\n\n _The more you know!_\n\n [pull/555]: https://github.com/rustwasm/wasm-pack/pull/555\n\n - **Fix links and Rust highlightning - [drager], [issue/513] [pull/514] [pull/516]**\n\n We had some broken links and missing Rust syntax highlighting in a few sections of the docs. This fixes that!\n\n [issue/513]: https://github.com/rustwasm/wasm-pack/issues/513\n [pull/514]: https://github.com/rustwasm/wasm-pack/pull/514\n [pull/516]: https://github.com/rustwasm/wasm-pack/pull/516\n\n## šŸŒ… 0.6.0\n\n- ### āœØ Features\n\n - **Add three build profiles and infrastructure for their toml config - [fitzgen], [issue/153] [issue/160] [pull/440]**\n\n When originally conceived, `wasm-pack` was exclusively a packaging and publishing tool, which naively assumed\n that the crate author would simply run `wasm-pack` when they were ready to publish a wasm package. As a result,\n `wasm-pack` always ran `cargo build` in `--release` mode. Since then, `wasm-pack` has grown into an integrated build\n tool used at all stages of development, from idea conception to publishing, and as such has developed new needs.\n\n In previous releases, we've supported a flag called `--debug` which will run `cargo build` in `dev` mode, which\n trades faster compilation speed for a lack of optimizations. We've renamed this flag to `--dev` to match `cargo`\n and added an additional flag, representing a third, intermediary, build profile, called `--profiling` which\n is useful for investigating performance issues. You can see all three flags and their uses in the table below:\n\n | Profile | Debug Assertions | Debug Info | Optimizations | Notes |\n | ------------- | ---------------- | ---------- | ------------- | ----------------------------------------------------------- |\n | `--dev` | Yes | Yes | No | Useful for development and debugging. |\n | `--profiling` | No | Yes | Yes | Useful when profiling and investigating performance issues. |\n | `--release` | No | No | Yes | Useful for shipping to production. |\n\n The meaning of these flags will evolve as the platform grows, and always be tied to the behavior of these flags\n in `cargo`. You can learn more about these in the [`cargo profile` documentation].\n\n This PR also introduces a way to configure `wasm-pack` in your `Cargo.toml` file that we intend to use much more\n in the future. As a largely convention-based tool, `wasm-pack` will never require that you configure it manually,\n however, as our community and their projects mature alongside the tool, it became clear that allowing folks the\n ability to drop down and configure things was something we needed to do to meet their needs.\n\n Currently, you can only configure things related to the above-mentioned build profiles. To learn more,\n [check out the documentation][profile-config-docs]. It leverages the `package.metadata.wasm-pack` key in your\n `Cargo.toml`, and looks like this:\n\n ```toml\n # Cargo.toml\n\n [package.metadata.wasm-pack.profile.dev.wasm-bindgen]\n # Should we enable wasm-bindgen's debug assertions in its generated JS glue?\n debug-js-glue = true\n # Should wasm-bindgen demangle the symbols in the \"name\" custom section?\n demangle-name-section = true\n # Should we emit the DWARF debug info custom sections?\n dwarf-debug-info = false\n ```\n\n As always- there are defaults for you to use, but if you love to configure (or have a project that requires it),\n get excited, as your options have grown now and will continue to!\n\n [profile-config-docs]: https://drager.github.io/wasm-pack/book/cargo-toml-configuration.html\n [`cargo profile` documentation]: https://doc.rust-lang.org/cargo/reference/manifest.html#the-profile-sections\n [issue/153]: https://github.com/rustwasm/wasm-pack/issues/153\n [issue/160]: https://github.com/rustwasm/wasm-pack/issues/160\n [pull/440]: https://github.com/rustwasm/wasm-pack/pull/440\n\n - **DEPRECATION: Rename `--debug` to `--dev` to match `cargo` - [fitzgen], [pull/439]**\n\n See the discussion of the build profiles feature above. This is a strict renaming of the previous `--debug` flag,\n which will now warn as deprecated.\n\n [pull/439]: https://github.com/rustwasm/wasm-pack/pull/439\n\n - **Add an option to pass an arbitrary set of arguments to `cargo build` - [torkve], [issue/455] [pull/461]**\n\n As an integrated build tool, `wasm-pack` orchestrates many secondary command line tools to build your package\n in a single command. Notably, one of these tools is `cargo`. `cargo` has a wide array of features and flags, and\n we couldn't reasonably expect to implement them all as first class features of `wasm-pack`. As a result, we've\n created the option to allow users to pass an arbitrary number of additional flags to `wasm-pack` by appending them\n to the `wasm-pack build` command, after passing `--`. For example:\n\n ```\n wasm-pack build examples/js-hello-world --mode no-install -- -Z offline\n ```\n\n In the above example, the flag `-Z offline` will be passed to `cargo build`. This feature is documented\n [here][cargo opts docs].\n\n [cargo opts docs]: https://drager.github.io/wasm-pack/book/commands/build.html#extra-options\n [torkve]: https://github.com/torkve\n [issue/455]: https://github.com/rustwasm/wasm-pack/issues/455\n [pull/461]: https://github.com/rustwasm/wasm-pack/pull/461\n\n - **Pre-build before wasm-pack publish - [csmoe], [issue/438] [pull/444]**\n\n Previously, if you ran `wasm-pack publish` before you had successfully run `wasm-pack build`,\n you'd receive an error that a package could not be found- because there would be no `pkg` or\n out-directory containing a `package.json`.\n\n In this situation, you would hope that `wasm-pack` would build your package for you when you\n ran `wasm-pack publish`. This is slightly complicated by the fact that not everyone wants to\n build their package to the default target or to a directory named `pkg`.\n\n To solve this, running `wasm-pack publish` before a successful build will give you an interactive\n prompt to build your package- allowing you to specify your out directory as well as the target you'd\n like to build to. Check it out in the gif below:\n\n ![pre-build publish workflow](https://user-images.githubusercontent.com/35686186/50500909-5984fe80-0a8f-11e9-9de6-43d1423b2969.gif)\n\n [issue/438]: https://github.com/rustwasm/wasm-pack/issues/438\n [pull/444]: https://github.com/rustwasm/wasm-pack/pull/444\n\n - **Generate self-.gitignore as part of pkg folder - [RReverser], [pull/453]**\n\n Since `wasm-pack` was first published, the `pkg` directory was intended to be treated as a\n build artifact, and as such should never be published to version control. This was\n never enforced by any assets generated by `wasm-pack`, however.\n\n Now, when building your package, `wasm-pack` will also generate a `.gitignore` file so that the\n `pkg`, or out-directory, will be ignored.\n\n If you use another version control tool, you'll need to still create or edit your own ignore file-\n pull requests to support other version control tools are welcome!\n\n If you require editing of the generated `package.json` or add additonal assets to your package\n before publishing, you'll want to remove the `.gitignore` file and commit to version control. We\n intend to have a solution that makes this workflow significantly easier in upcoming releases!\n\n [RReverser]: https://github.com/RReverser\n [pull/453]: https://github.com/rustwasm/wasm-pack/pull/453\n\n - **Support cargo workspaces - [fitzgen], [issue/252] [issue/305] [pull/430]**\n\n Workspaces are a well-liked and used feature of cargo that allow you to build multiple crates\n in a single cargo project. Because of how `wasm-pack` handled paths for `target` and out-directories,\n we did not support cargo workspaces out of the box. Now they should work well and the feature is\n well guarded by tests!\n\n [issue/252]: https://github.com/rustwasm/wasm-pack/issues/252\n [issue/305]: https://github.com/rustwasm/wasm-pack/issues/305\n [pull/430]: https://github.com/rustwasm/wasm-pack/pull/430\n\n - **Use a global cache for all downloaded binaries - [alexcrichton], [pull/426]**\n\n `wasm-pack` is an integrated build tool that orchestrates several other command line tools to build\n your wasm project for you. How `wasm-pack` does this has evolved significantly since it's early versions.\n In the last version, a `bin` directory was created to house the tool binaries that `wasm-pack` needed to\n build our project, but this had several limitations. Firstly, it created a `bin` directory in your project's\n root, which could be confusing. Secondly, it meant that sharing these tools across multiple projects was\n not possible. We did this because it gaves us the fine-grained control over the version of these tools that\n you used.\n\n Now, `wasm-pack` will not generate a `bin` directory, but rather will use a global cache. We retain the\n fine-grained control over the versions of these tools that are used, but allow multiple projects that use\n the same tools at the same versions to share the already installed asset. Your global cache will generally\n be in your user's home directory- we use the [`dirs` crate] to determine where to place this global cache.\n This is not currently customizable but is something we intend to look into doing!\n\n This feature ensures that `wasm-pack` users are downloading a minimal number of binaries from the network,\n which, for `wasm-pack` users with multiple projects, should speed up build times.\n\n [`dirs` crate]: https://docs.rs/dirs/1.0.4/dirs/fn.cache_dir.html\n [pull/426]: https://github.com/rustwasm/wasm-pack/pull/426\n\n- ### šŸ¤• Fixes\n\n - **Fix `pack`, `login`, and `publish` for Windows users - [danwilhelm], [issue/277] [pull/489]**\n\n Rust's behavior for spawning processes on some Windows targets introduced an interesting case where\n Rust would fail unless the command was explicitly spawned with a prepended `cmd /c`. This failure\n of `wasm-pack` was well noticed by our community - and thanks to the efforts of `danwilhelm` is now\n fixed! You can read more on the background of this issue in [rust-lang/rust issue/44542].\n\n [rust-lang/rust issue/44542]: https://github.com/rust-lang/rust/pull/44542\n [issue/277]: https://github.com/rustwasm/wasm-pack/issues/277\n [pull/489]: https://github.com/rustwasm/wasm-pack/pull/489\n\n - **Validate `--target` argument - [csmoe], [issue/483] [pull/484]**\n\n For a few releases now, `wasm-pack` has supported allowing users to specifying the target module system\n they'd like their package built for- `browser`, `nodejs`, and `no-modules`. We did not however, validate\n this input, and so if a user made even a slight mistake, e.g. `node`, `wasm-pack` would not catch the\n error and would build your project using the default, `browser`. This is of course, surprising, and\n unpleasant behavior and so now we'll error out with a message containing the supported target names.\n\n [issue/483]: https://github.com/rustwasm/wasm-pack/issues/483\n [pull/484]: https://github.com/rustwasm/wasm-pack/pull/484\n\n - **Fix login - [danwilhelm], [issue/486] [pull/487]**\n\n [danwilhelm]: https://github.com/danwilhelm\n [issue/486]: https://github.com/rustwasm/wasm-pack/issues/486\n [pull/487]: https://github.com/rustwasm/wasm-pack/pull/487\n\n - **Eliminate unecessary escaping in build success terminal output - [huangjj27], [issue/390] [pull/396]**\n\n Previously, on some systems, a successful `wasm-pack build` would print a unfortunate looking string:\n\n ```\n | :-) Your wasm pkg is ready to publish at \"\\\\\\\\?\\\\C:\\\\Users\\\\Ferris\\\\tmp\\\\wasm-bug\\\\pkg\".\n ```\n\n We've updated this to make sure the path to your project is well-formed, and most importantly,\n human-readable.\n\n [issue/390]: https://github.com/rustwasm/wasm-pack/issues/390\n [pull/396]: https://github.com/rustwasm/wasm-pack/pull/396\n\n - **Copy license file(s) to out directory - [mstallmo], [issue/407] [pull/411]**\n\n Since `wasm-pack` was first published, we've copied over your `Cargo.toml` license definition over to\n your `package.json`. However, we overlooked copying the actual `LICENSE` files over! Now we do!\n\n [issue/407]: https://github.com/rustwasm/wasm-pack/issues/407\n [pull/411]: https://github.com/rustwasm/wasm-pack/pull/411\n\n - **Don't require cdylib crate-type for testing - [alexcrichton], [pull/442]**\n\n `wasm-pack` was unecssarily checking `Cargo.toml` for the `cdylib` crate type during calls to `wasm-pack test`.\n The `cdylib` output isn't necessary for the `wasm-pack test` stage because `wasm-bindgen` isn't being run over\n a wasm file during testing. This check is now removed!\n\n [pull/442]: https://github.com/rustwasm/wasm-pack/pull/442\n\n - **Fix wasm-bindgen if lib is renamed via `lib.name` - [alexcrichton], [issue/339] [pull/435]**\n\n In some circumstances, a library author may wish to specify a `name` in the `[package]` portion of their\n `Cargo.toml`, as well as a different `name` in the `[lib]` portion, e.g.:\n\n ```toml\n [package]\n name = \"hello-wasm\"\n\n [lib]\n name = \"wasm-lib\"\n ```\n\n This would cause the `wasm-bindgen` build stage of `wasm-pack` to error out because `wasm-pack` would attempt\n to run `wasm-bindgen-cli` on a path using the `[package]` name, which wouldn't exist (because it would be using\n the `[lib]` name). Now it works- thanks to more usage of [`cargo_metadata`] in `wasm-pack` internals!\n\n [`cargo_metadata`]: https://crates.io/crates/cargo_metadata\n [issue/339]: https://github.com/rustwasm/wasm-pack/issues/339\n [pull/435]: https://github.com/rustwasm/wasm-pack/pull/435\n\n - **Print standard error only once for failing commands - [fitzgen], [issue/422] [pull/424]**\n\n Previously, `wasm-pack` may have printed `stderr` twice in some circumstances. This was both confusing and not\n a pleasant experience, so now we've ensued that `wasm-pack` prints `stderr` exactly once! (It's hard enough to have\n errors, you don't want `wasm-pack` rubbing it in, right?)\n\n [issue/422]: https://github.com/rustwasm/wasm-pack/issues/422\n [pull/424]: https://github.com/rustwasm/wasm-pack/pull/424\n\n - **Add no-modules to --target flag's help text - [fitzgen], [issue/416] [pull/417]**\n\n This is an interesting one! `fitzgen` very reasonably filed an issue asking to add `wasm-bindgen`'s\n `--target no-modules` feature to `wasm-pack`. This was confusing as this feature was indeed already implemented,\n and documented- BUT, notably missing from the `wasm-pack --help` text. We've fixed that now- and it was an omission\n so glaring we definitely considered it a bug!\n\n [issue/416]: https://github.com/rustwasm/wasm-pack/issues/416\n [pull/417]: https://github.com/rustwasm/wasm-pack/pull/417\n\n- ### šŸ› ļø Maintenance\n\n - **Replace `slog` with `log` - [alexcrichton], [issue/425] [pull/434]**\n\n For internal maintenance reasons, as well as several end-user ones, we've migrated away from the `slog` family\n of crates, and are now using the `log` crate plus `env_logger`. Now, `wasm-pack` won't create a `wasm-pack.log`.\n Additionally, enabling logging will now be done through `RUST_LOG=wasm_pack` instead of `-v` flags.\n\n [issue/425]: https://github.com/rustwasm/wasm-pack/issues/425\n [pull/434]: https://github.com/rustwasm/wasm-pack/pull/434\n\n - **Move binary installation to its own crate - [drager], [issue/384] [pull/415]**\n\n In `wasm-pack 0.5.0`, we move away from `cargo install`ing many of the tools that `wasm-pack` orchestrates. Because\n we used `cargo install`, this required an end user to sit through the compilation of each tool, which was a\n prohibitively long time. We moved, instead, to building, and then installing, binaries of the tools. This sped up\n build times dramatically!\n\n This pattern has been very beneficial to `wasm-pack` and is potentially something that could be beneficial to other\n projects! As a result, we've refactored it out into a crate and have published it as it's own crate, [`binary-install`].\n\n [`binary-install`]: https://crates.io/crates/binary-install\n [drager]: https://github.com/drager\n [issue/384]: https://github.com/rustwasm/wasm-pack/issues/384\n [pull/415]: https://github.com/rustwasm/wasm-pack/pull/415\n\n - **Replace internal `Error` with `failure::Error` - [alexcrichton], [pull/436]**\n\n The story of error message handling in `wasm-pack` has not been the prettiest. We originally were manually implementing\n errors, adding the [`failure` crate] at one point, but not fully updating the entire codebase. With this PR, we are\n nearly completely handling errors with `failure`, bringing the code into a much more maintainable and\n pleasant-to-work-on place.\n\n [`failure` crate]: https://crates.io/crates/failure\n [pull/436]: https://github.com/rustwasm/wasm-pack/pull/436\n\n - **Update `mdbook` version used by Travis - [fitzgen], [pull/433]**\n\n [pull/433]: https://github.com/rustwasm/wasm-pack/pull/433\n\n - **Read the `Cargo.toml` file only once - [fitzgen], [issue/25] [pull/431]**\n\n This is a very fun one since it fixes one of the original issues filed by `ag_dubs` at the very beginning of `wasm-pack`\n development. In a rush to implement a POC tool, `ag_dubs` noted for posterity that the `Cargo.toml` was being read\n multiple times (twice), when it did not need to be. Thanks to `fitzgen` now it's read only once! A minor performance\n improvement in the scheme of things, but a nice one :)\n\n [issue/25]: https://github.com/rustwasm/wasm-pack/issues/25\n [pull/431]: https://github.com/rustwasm/wasm-pack/pull/431\n\n - **Use `name` field for Travis CI jobs - [fitzgen], [pull/432]**\n\n [pull/432]: https://github.com/rustwasm/wasm-pack/pull/432\n\n - **Add a test for build command - [huangjj27], [pull/408]**\n\n [huangjj27]: https://github.com/huangjj27\n [pull/408]: https://github.com/rustwasm/wasm-pack/pull/408\n\n - **Test paths on Windows - [xmclark], [issue/380] [pull/389]**\n\n [xmclark]: https://github.com/xmclark\n [issue/380]: https://github.com/rustwasm/wasm-pack/issues/380\n [pull/389]: https://github.com/rustwasm/wasm-pack/pull/389\n\n - **Fix typo in test function name for copying the README - [mstallmo], [pull/412]**\n\n [pull/412]: https://github.com/rustwasm/wasm-pack/pull/412\n\n- ### šŸ“– Documentation\n\n - **Complete template deep dive docs - [danwilhelm], [issue/345] [issue/346] [pull/490]**\n\n In a rush to publish a release, `ag_dubs` left some \"Coming soon!\" comments on most pages\n of the \"Template Deep Dive\" docs. These docs help walk new users through the boilerplate\n that using the `wasm-pack` template generates for you. Thanks so much to `danwilhem` for\n picking this up and doing an excellent job!\n\n [issue/345]: https://github.com/rustwasm/wasm-pack/issues/345\n [issue/346]: https://github.com/rustwasm/wasm-pack/issues/346\n [pull/490]: https://github.com/rustwasm/wasm-pack/pull/490\n\n - **Minor docs updates - [fitzgen], [issue/473] [pull/485]**\n\n [issue/473]: https://github.com/rustwasm/wasm-pack/issues/473\n [pull/485]: https://github.com/rustwasm/wasm-pack/pull/485\n\n## šŸŒ„ 0.5.1\n\n- ### šŸ¤• Fixes\n\n - **Child Process and output management - [fitzgen], [issue/287] [pull/392]**\n\n Not exactly a \"fix\", but definitely a huge improvment in how child processes and their\n output are handled by `wasm-pack`. Ever sat at a long prompt from `wasm-pack` and\n wondered what was happening? No longer! Did `wasm-pack` eat your test output- no more!\n\n [issue/287]: https://github.com/rustwasm/wasm-pack/issues/287\n [pull/392]: https://github.com/rustwasm/wasm-pack/pull/392\n\n - **Less scary missing field messages - [mstallmo], [issue/393] [pull/394]**\n\n After watching a livestream of someone using `wasm-pack`, [fitzgen] noted that folks\n seemed pretty alarmed by the loud warning about missing optional manifest fields.\n As a result, we are now downgrading those messages from WARN to INFO, and consolidating\n them on a single line.\n\n [issue/393]: https://github.com/rustwasm/wasm-pack/issues/393\n [pull/394]: https://github.com/rustwasm/wasm-pack/pull/394\n\n - **Add `exit_status` to CLI errors - [konstin], [issue/291] [pull/387]**\n\n We'd been hiding these- but we shouldn't have been!\n\n [konstin]: https://github.com/konstin\n [issue/291]: https://github.com/rustwasm/wasm-pack/issues/291\n [pull/387]: https://github.com/rustwasm/wasm-pack/pull/387\n\n - **Remove lingering forced nightly usage - [alexcrichton], [pull/383]**\n\n In 0.5.0 we removed all forced nightly usage as we depend on `~1.30` which is now\n available on both nightly and beta channels! We had a bit of a race condition with\n that PR and the `wasm-pack test` PR, and missed a few as a result! This removes all\n lingering forced nightly, which only affected the `wasm-pack test` command.\n\n [pull/383]: https://github.com/rustwasm/wasm-pack/pull/383\n\n - **Fix `wasm-bindgen-test` dependency error message - [fitzgen], [issue/377] [pull/378]**\n\n The error message about missing the `wasm-bindgen-test` dependency errantly stated\n that the user was missing a `wasm-bindgen` dependency! We've fixed it to correctly\n state the missing dependency now.\n\n [issue/377]: https://github.com/rustwasm/wasm-pack/issues/377\n [pull/378]: https://github.com/rustwasm/wasm-pack/pull/378\n\n - **Fix prerequisites links in docs - [fitzgen], [pull/376]**\n\n [pull/376]: https://github.com/rustwasm/wasm-pack/pull/376\n\n- ### šŸ› ļø Maintenance\n\n - **Leverage `failure::Error` consistently - [drager], [issue/280] [pull/401]**\n\n This PR finally makes it so that `wasm-pack` is handling errors in a consistent\n way across the codebase.\n\n [drager]: https://github.com/drager\n [issue/280]: https://github.com/rustwasm/wasm-pack/issues/280\n [pull/401]: https://github.com/rustwasm/wasm-pack/pull/401\n\n## ā˜€ļø 0.5.0\n\n- ### āœØ Features\n\n - #### **Website!** - [ashleygwilliams], [pull/246]\n\n We have a website now. It has the installer and links to documentation. In the future,\n we hope to have calls to action for folks first coming to the site who are looking to\n do specific things- these will help them find the docs and tutorials they need to.\n\n This PR also has a complete rework of our documentation.\n\n Check it out [here](https://drager.github.io/wasm-pack/)!\n\n - #### šŸ± Module Support\n\n - **BREAKING: use correct `package.json` keys for generated JavaScript - [ashleygwilliams], [issue/309] [pull/312]**\n\n This is marked as potentially breaking because it changes the `package.json` keys that\n are generated by the project.\n\n Previously, we generated a JavaScript file and placed it in the `main` key, regardless\n of what you were targeting, ES6 and Node.js alike.\n\n We have received a lot of requests for `wasm-pack` to generate \"isomorphic\" packages,\n that contain assets that could work on both Node.js and ES6, and this led to us\n looking more closely at how we are using `package.json`.\n\n With this release, we will do the following:\n\n - `--target browser`: By default, we generate JS that is an ES6 module. We used to put\n this in the `main` field. Now we put it in the `module` field. We also add\n `sideEffects: false` so that bundlers that want to tree shake can.\n\n - `--target nodejs`: This target doesn't change. We put generated JS that is a\n CommonJS module in the `main` key.\n\n - `--target no-modules`: This is a new target. For this target we generate bare JavaScript.\n This code is put in a `browser` field.\n\n You can see the structs that represent each target's expected `package.json` [here](https://github.com/rustwasm/wasm-pack/tree/master/src/manifest/npm).\n\n Thanks so much to [bterlson] for his help in sorting this out for us!\n\n [bterlson]: https://github.com/bterlson\n [issue/309]: https://github.com/rustwasm/wasm-pack/issues/309\n [pull/312]: https://github.com/rustwasm/wasm-pack/pull/312\n\n - #### šŸ› ļø New Commands\n\n - **`wasm-pack init` is now `wasm-pack build` - [csmoe], [issue/188] [pull/216]**\n\n When this project was first conceived, we imagined it would be simply a way to package\n up generate wasm and js and publish it to npm. Here we are at version `0.5.0` and we\n have become much more- an integrated build tool!\n\n As a result, the original command `init` does a lot more than that these days. We've\n renamed the command to better reflect the work it's actually doing. `init` will still\n work, but is deprecated now, and we will eventually remove it.\n\n [csmoe]: https://github.com/csmoe\n [issue/188]: https://github.com/rustwasm/wasm-pack/issues/188\n [pull/216]: https://github.com/rustwasm/wasm-pack/pull/216\n\n - **add new command: `wasm-pack test` - [fitzgen], [pull/271]**\n\n This is an experimental new command that will run your tests in Node.js or a headless\n browser using `wasm-pack test`. Check out this [tutorial](https://rustwasm.github.io/wasm-bindgen/wasm-bindgen-test/index.html)\n to learn more!\n\n [pull/271]: https://github.com/rustwasm/wasm-pack/pull/271\n\n - **add 2FA support to `wasm-pack publish` - [mstallmo], [issue/257] [pull/282]**\n\n We've been wrapping the `npm login` and `npm publish` commands as `wasm-pack login`\n and `wasm-pack publish` for a while now- but we didn't fully support two factor\n authentication. Now we do! (Be safe out there! 2FA is good for everyone!)\n\n [issue/257]: https://github.com/rustwasm/wasm-pack/issues/257\n [pull/282]: https://github.com/rustwasm/wasm-pack/pull/282\n\n - #### šŸŽ New Flags\n\n - **New target, bare JavaScript: `--target no-modules` - [ashleygwilliams], [issue/317] [pull/327]**\n\n `wasm-bindgen` offers a `no-modules` flag that until now, we didn't support. This flag\n produces bare, no modules JavaScript. So if that's your thing, this target is for you!\n\n [issue/317]: https://github.com/rustwasm/wasm-pack/issues/317\n [pull/327]: https://github.com/rustwasm/wasm-pack/pull/327\n\n - **`--access` flag for `wasm-pack` publish - [ashleygwilliams], [issue/297] [pull/299]**\n\n Many of our tutorials use scopes to help prevent folks from attempting to publish\n packages that will lead to npm Registry errors because the package name already exists.\n\n However, by default, scoped packages are assumed by the npm registry to be private, and\n the ability to publish private packages to the npm registry is a paid feature. Worry not!\n Now you can pass `--access public` to `wasm-pack publish` and publish scoped packages\n publicly.\n\n [issue/297]: https://github.com/rustwasm/wasm-pack/issues/297\n [pull/299]: https://github.com/rustwasm/wasm-pack/pull/299\n\n - #### āœ… New Checks\n\n - **rustc version check - [ashleygwilliams], [issue/351] [pull/353]**\n\n Now that we have a new fangled installer, there's a chance that folks might install `wasm-pack`\n and not have Rust installed. Additionally, now that the features we required from the `nightly`\n channel of Rust have moved to `beta`- we don't need to enforce `nightly`.\n\n As of this release, we will check that your Rust version is above `1.30.0`. You can be on\n either the `nightly` or `beta` channel and all of `wasm-pack`s calls to `cargo` will\n respect that.\n\n Really hate this? You can pass `--mode force` to `wasm-pack` to skip this check. I hope you know\n what you're doing!\n\n - **coordinating wasm-bindgen versions and installing from binaries for improved speed - [datapup], [issue/146] [pull/244] [pull/324]**\n\n This is the true gem of this release. Have you been frustrated by how long `wasm-pack` takes to\n run? Overusing `--mode no-install`? This is the release you're looking for.\n\n Many releases back we realized that folks were struggling to keep the `wasm-bindgen` library\n that their project used in sync with the `wasm-bindgen` CLI application which `wasm-pack`\n runs for you. This became such an issue that we opted to force install `wasm-bindgen` to ensure\n that every `wasm-pack` user had the latest version.\n\n Like many technical solutions, this solved our original problem, but caused a new one. Now, we\n we are forcing a `cargo install` of `wasm-bindgen` on every run, and that means downloading\n and compiling `wasm-bindgen` everytime you want to run `wasm-pack`. That's unacceptable!\n\n We're happy to announce that we have a pretty great solution, and several more planned for\n future releases. As of this release, we will read your `Cargo.lock` to find the version of\n `wasm-bindgen` you are using in your local project. We will attempt to fetch a binary version\n of `wasm-bindgen` that matches your local version. We place that binary local to your project,\n and use it when you run `wasm-pack build`. The next time you run `wasm-pack build` we'll use\n that binary, instead of fetching a new one. We still fall back to `cargo install` for\n less common architectures but this is a huge speed improvement. Check out these benchmarks!\n\n ##### `wasm-pack` v0.4.2\n\n ```\n $ time wasm-pack init # fresh build\n real 1m58.802s\n user 14m49.679s\n sys 0m24.957s\n\n $ time wasm-pack init # re-build\n real 0m56.953s\n user 11m12.075s\n sys 0m18.835s\n\n $ time wasm-pack init -m no-install # re-build with no-install\n real 0m0.091s\n user 0m0.052s\n sys 0m0.042s\n ```\n\n ##### `wasm-pack` v0.5.0\n\n ```\n $ time wasm-pack build # fresh build\n real 1m3.350s\n user 3m46.912s\n sys 0m6.057s\n\n $ time wasm-pack build # re-build\n real 0m0.230s\n user 0m0.185s\n sys 0m0.047s\n\n $ time wasm-pack build -m no-install # re-build with no-install\n real 0m0.104s\n user 0m0.066s\n sys 0m0.041s\n ```\n\n [datapup]: https://github.com/datapup\n [issue/146]: https://github.com/rustwasm/wasm-pack/issues/146\n [pull/244]: https://github.com/rustwasm/wasm-pack/pull/244\n [pull/324]: https://github.com/rustwasm/wasm-pack/pull/324\n\n - **enforce `cargo build` with `--lib` - [ashleygwilliams], [issue/303] [pull/330]**\n\n Right now, `wasm-pack` only works on Rust library projects. But sometimes, if you're\n new to Rust, you might end up having a `main.rs` in your project, just by mistake.\n Some folks ran into this and realized that it can cause issues!\n\n As a result, we are enforcing that `cargo build` only build the library at this time.\n\n Want to use `wasm-pack` on a binary application? We're interested in hearing from you!\n Checkout [issue/326] and please comment! We want to support binary applicaitons in\n the future and are always happy and curious to hear about how folks use `wasm-pack`!\n\n [issue/326]: https://github.com/rustwasm/wasm-pack/issues/326\n [issue/303]: https://github.com/rustwasm/wasm-pack/issues/303\n [pull/330]: https://github.com/rustwasm/wasm-pack/pull/330\n\n - #### Installers and Releases\n\n - **Appveyor Windows Pre-Built binaries - [alexcrichton], [issue/147] [pull/301]**\n\n We finally got Appveyor to publish pre-built binaries to GitHub releases.\n Aside: I really wish there were an easier way to test and debug this stuff.\n\n [alexcrichton]: https://github.com/alexcrichton\n [issue/147]: https://github.com/rustwasm/wasm-pack/issues/147\n [pull/301]: https://github.com/rustwasm/wasm-pack/pull/301\n\n - **new experimental installer - [alexcrichton], [pull/307]**\n\n Whew, this one is exciting. Up until now, `wasm-pack` has been distributed using\n `cargo install`. This is not ideal for several reasons. Updating is confusing,\n and every time it's installed the user has to wait for it to compile- right at the\n moment they just want to hurry up and use it already.\n\n Say hello to the new `wasm-pack` installer- we have an executable for Windows\n and a `curl` script for \\*nix users. Not pleased with that? File an issue for your\n preferred distribution method and we'll do our best to get it working!\n\n This is experimental- so please try it out and file issues as you run into things!\n You'll always be able to use `cargo install` as a backup.\n\n Checkout the new installer [here](https://drager.github.io/wasm-pack/installer/)!\n\n [pull/307]: https://github.com/rustwasm/wasm-pack/pull/307\n\n- ### šŸ› ļø Maintenance\n\n - **testing fixture strategy improvements - [fitzgen], [pull/211] [pull/323]**\n\n [pull/211]: https://github.com/rustwasm/wasm-pack/pull/211\n [pull/323]: https://github.com/rustwasm/wasm-pack/pull/323\n\n - **split testing utils into separate files - [csmoe], [issue/231] [pull/216]**\n\n [issue/231]: https://github.com/rustwasm/wasm-pack/issues/231\n [pull/216]: https://github.com/rustwasm/wasm-pack/pull/216\n\n - **update dependencies - [ashleygwilliams], [issue/319] [pull/320]**\n\n [issue/319]: https://github.com/rustwasm/wasm-pack/issues/319\n [pull/320]: https://github.com/rustwasm/wasm-pack/pull/320\n\n- ### šŸ“– Documentation\n\n - **improve readability of warnings about missing optional fields - [twilco], [pull/296]**\n\n A little punctuation goes a long way. Error message improvement PRs are the best.\n\n [twilco]: https://github.com/twilco\n [pull/296]: https://github.com/rustwasm/wasm-pack/pull/296\n\n - **update links in README - [alexcrichton], [pull/300]**\n\n We had a real dicey documentation situation for a while. Sorry about that, and thank\n you SO MUCH to all the folks who filed PRs to fix it.\n\n [pull/300]: https://github.com/rustwasm/wasm-pack/pull/300\n\n - **fix broken links in book by using relative paths - [mstallmo], [issue/325] [pull/328]**\n\n [mstallmo]: https://github.com/mstallmo\n [issue/325]: https://github.com/rustwasm/wasm-pack/issues/325\n [pull/328]: https://github.com/rustwasm/wasm-pack/pull/328\n\n## āœØ 0.4.2\n\n- #### šŸ¤• Fixes\n\n - **recognize `[dependencies.wasm-bindgen]` during dep check in `init` - [ashleygwilliams], [issue/221] [pull/224]**\n\n When we originally implemented the dependency check in `wasm-pack init` we naively only checked for the\n \"simple\" dependency declaration, `[dependencies] wasm-bindgen=\"0.2\"`. However! This is not the only way\n to declare this dependency, and it's not the ideal way to do it if you want to specify features from the\n crate. Now that a bunch of folks want to use `features = [\"serde-serialize\"]` we ran into a bunch of folks\n having issues with our naive dependency checker! Thanks so much to [turboladen] for filing the very detailed\n issue that helped us solve this quickly!\n\n PSSSST! Curious what `features = [\"serde-serialize\"]` with `wasm-bindgen` actually does? It's awesome:\n\n > It's possible to pass data from Rust to JS not explicitly supported in the [Feature Reference](./feature-reference.md) by serializing via [Serde](https://github.com/serde-rs/serde).\n\n Read the [Passing arbitrary data to JS docs] to learn more!\n\n [Passing arbitrary data to JS docs]: https://github.com/rustwasm/wasm-bindgen/blob/master/guide/src/reference/arbitrary-data-with-serde.md\n [turboladen]: https://github.com/turboladen\n [issue/221]: https://github.com/rustwasm/wasm-pack/issues/221\n [pull/224]: https://github.com/rustwasm/wasm-pack/pull/224\n\n - **improve UX of publish and pack commands - [Mackiovello], [pull/198]**\n\n Previous to this fix, you would need to be in the parent directory of the `/pkg` dir to successfully run\n `pack` or `publish`. This was pretty crummy! Thankfully, [Mackiovello] swooped in with a fix, that you can\n find documented in the [pack and publish docs]!\n\n [Mackiovello]: https://github.com/Mackiovello\n [pull/198]: https://github.com/rustwasm/wasm-pack/pull/198\n [pack and publish docs]: https://github.com/rustwasm/wasm-pack/blob/05e4743c22b57f4c4a1bfff1df1d2cc1a595f523/docs/pack-and-publish.md\n\n - **use `PathBuf` instead of `String` for paths - [Mackiovello], [pull/220]**\n\n This is mostly a maintenance PR but does fix one very small bug- depending on if you add a trailing slash to\n a path that you pass to `init`, you might have seen an extra `/`! Now that we're using a proper Type to\n handle this, that's much better, and in general, all the operations using paths are more robust now.\n\n [pull/220]: https://github.com/rustwasm/wasm-pack/pull/220\n\n- #### šŸ“– Documentation\n\n - **update docs and tests to eliminate no longer necessary feature flags - [ashleygwilliams], [pull/226]**\n\n The Rust 2018 edition marches on and we are seeing feature flags drop like flies :) Instead of a whole slew\n of feature flags, we now only need one, `#![feature(use_extern_macros)]`, and that one is also not long for\n this world :)\n\n [pull/226]: https://github.com/rustwasm/wasm-pack/pull/226\n\n## ā­ 0.4.1\n\n- #### šŸ¤• Fixes\n\n - **fix `files` key value for projects build for `nodejs` target - [ashleygwilliams], [issue/199] [pull/205]**\n\n We became aware that the `files` key in `package.json` did not include the additional `_bg.js` file that\n `wasm-bindgen` generates for projects being built for the `nodejs` target. This resulted in the file not\n being included in the published package and resulted in a `Module Not Found` error for folks.\n\n This was a group effort from [mciantyre] with [pull/200] and [Brooooooklyn] with [pull/197]. Thank you so\n much for your diligence and patience while we sorted through it.\n\n [mciantyre]: https://github.com/mciantyre\n [Brooooooklyn]: https://github.com/Brooooooklyn\n [issue/199]: https://github.com/rustwasm/wasm-pack/issues/199\n [pull/205]: https://github.com/rustwasm/wasm-pack/pull/205\n [pull/197]: https://github.com/rustwasm/wasm-pack/pull/197\n [pull/200]: https://github.com/rustwasm/wasm-pack/pull/200\n\n- #### šŸ› ļø Maintenance\n\n - **clean up `quicli` remnants - [SoryRawyer], [pull/193]**\n\n In [v0.3.0] we removed the `quicli` dependency, however there were a few remnants\n left behind. They are now removed!\n\n [SoryRawyer]: https://github.com/SoryRawyer\n [pull/193]: https://github.com/rustwasm/wasm-pack/pull/193\n [v0.3.0]: https://github.com/rustwasm/wasm-pack/blob/master/CHANGELOG.md#-030\n\n- #### šŸ“– Documentation\n\n - **DOCUMENT EVERYTHING!! and deny missing docs for all future development - [fitzgen], [pull/208]**\n\n The `wasm-pack` team has worked hard on tutorial documentation and keeping the codebase as self-explanatory\n as possible, but we have been slowly accruing a documentation debt. This amazing PR, landed just moments\n before this point release and was just too good not to include. Thank you so much, [fitzgen]!\n\n [fitzgen]: https://github.com/fitzgen\n [pull/208]: https://github.com/rustwasm/wasm-pack/pull/208\n\n - **fix README code example - [steveklabnik], [pull/195]**\n\n The code example in our `README.md` was missing a critical `pub`. It's there now!\n\n [pull/195]: https://github.com/rustwasm/wasm-pack/pull/195/files\n\n - **fix README markup - [Hywan], [pull/202]**\n\n There was an errant `` ` `` - it's gone now!\n\n [Hywan]: https://github.com/Hywan\n [pull/202]: https://github.com/rustwasm/wasm-pack/pull/202\n\n## šŸŒŸ 0.4.0\n\nThis release has a ton of awesome things in it, but the best thing is that\nalmost all of this awesome work is brought to you by a **new** contributor\nto `wasm-pack`. Welcome ya'll! We're so glad to have you!\n\n### āœØ Features\n\n- #### šŸŽ New Flags\n\n - **`--mode` flag for skipping steps when calling `init` - [ashleygwilliams], [pull/186]**\n\n After teaching and working with `wasm-pack` for some time, it's clear that people would\n like the flexibility to run some of the steps included in the `init` command and not others.\n This release introduces a `--mode` flag that you can pass to `init`. The two modes currently\n available are `skip-build` and `no-installs` and they are explained below. In the future,\n we are looking to change the `init` interface, and potentially to split it into two commands.\n If you have thoughts or opinions on this, please weigh in on [issue/188]!\n\n [issue/188]: https://github.com/ashleygwilliams/wasm-pack/issues/188\n [pull/186]: https://github.com/ashleygwilliams/wasm-pack/pull/186\n\n - **`skip-build` mode - [kohensu], [pull/151]**\n\n ```\n wasm-pack init --mode skip-build\n ```\n\n Sometimes you want to run some of the shorter meta-data steps that\n `wasm-pack init` does for you without all the longer build steps. Now\n you can! Additionally, this PR was a fantastic refactor that allows even\n more custom build configurations will be simple to implement!\n\n [kohensu]: https://github.com/kohensu\n [pull/151]: https://github.com/ashleygwilliams/wasm-pack/pull/151\n\n - **`no-installs` mode - [ashleygwilliams], [pull/186]**\n\n ```\n wasm-pack init --mode no-installs\n ```\n\n Sometimes you want to run `wasm-pack` and not have it modify your global\n env by installing stuff! Or maybe you are just in a hurry and trust your\n env is set up correctly- now the `--mode no-install` option allows you to\n do this.\n\n - **`--debug` - [clanehin], [pull/127]**\n\n ```\n wasm-pack init --debug\n ```\n\n Find yourself needing to compile your Rust in `development` mode? You can now\n pass the `--debug` flag to do so! Thanks so much to [clanehin] for filing\n [issue/126] for this feature... and then implementing it!\n\n [pull/127]: https://github.com/ashleygwilliams/wasm-pack/pull/127\n [issue/126]: https://github.com/ashleygwilliams/wasm-pack/issues/126\n [clanehin]: https://github.com/clanehin\n\n- #### āœ… New Checks\n\n - **ensure you have `cdylib` crate type - [kendromelon], [pull/150]**\n\n One of the biggest mistakes we've seen beginners make is forgetting to declare\n the `cdylib` crate type in their `Cargo.toml` before running `wasm-pack init`.\n This PR fixes that, and comes from someone who ran into this exact issue learning\n about `wasm-pack` at [JSConfEU]! Love when it works out like this.\n\n [JSConfEU]: https://2018.jsconf.eu/\n [kendromelon]: https://github.com/kedromelon\n [pull/150]: https://github.com/ashleygwilliams/wasm-pack/pull/150\n\n - **ensure you have declared wasm-bindgen as a dep - [robertohuertasm], [pull/162]**\n\n Another easy mistake to make is to forget to declare `wasm-bindgen` as a\n dependency in your `Cargo.toml`. Now `wasm-pack` will check and make sure you\n have it set before doing a bunch of long build steps :)\n\n [robertohuertasm]: https://github.com/robertohuertasm\n [pull/162]: https://github.com/ashleygwilliams/wasm-pack/pull/162\n\n - **ensure you are running `nightly` - [FreeMasen], [pull/172]**\n\n `wasm-pack` currently requires that you run it with `nightly` Rust. Now, `wasm-pack`\n will make sure you have `nightly` installed and will ensure that `cargo build` is run\n with `nightly`. Thanks so much to [FreeMasen] for filing [issue/171] and fixing it!\n\n [FreeMasen]: https://github.com/FreeMasen\n [issue/171]: https://github.com/ashleygwilliams/wasm-pack/issues/171\n [pull/172]: https://github.com/ashleygwilliams/wasm-pack/pull/172\n\n### šŸ¤• Fixes\n\n- **fixed broken progress bar spinner - [migerh], [pull/164]**\n\n Oh no! We broke the progress bar spinner in version 0.3.0. Thankfully, it's\n fixed now- with a thoughtful refactor that also makes the underlying code\n sounder overall.\n\n[migerh]: https://github.com/migerh\n[pull/164]: https://github.com/ashleygwilliams/wasm-pack/pull/164\n\n### šŸ› ļø Maintenance\n\n- **WIP bot - [ashleygwilliams] & [mgattozzi], [issue/170]**\n\n We've got a lot of work happening on `wasm-pack` so it's good to have a bit\n of protection from accidentally merging a Work In Progress. As a result, we\n now have the [WIP Github App] set up on `wasm-pack`. Great suggestion [mgattozzi]!\n\n [WIP Github App]: https://github.com/wip/app\n [issue/170]: https://github.com/ashleygwilliams/wasm-pack/issues/170\n\n- **modularize `command.rs` - [ashleygwilliams], [pull/182]**\n\n Thanks to the growth of `wasm-pack`, `command.rs` was getting pretty long.\n We've broken it out into per command modules now, to help make it easier to\n read and maintain!\n\n [pull/182]: https://github.com/ashleygwilliams/wasm-pack/pull/182\n\n- **improve PoisonError conversion - [migerh], [pull/187]**\n\n As part of the awesome progress bar spinner fix in [pull/164], [migerh] introduced\n a small concern with an `unwrap` due to an outstanding need to convert `PoisonError`\n into `wasm-pack`'s custom `Error`. Though not a critical concern, [migerh] mitigated\n this right away by replacing `std::sync::RwLock` with the [`parking_lot` crate]!\n This cleaned up the code even more than the previous patch!\n\n [`parking_lot` crate]: https://github.com/Amanieu/parking_lot\n [pull/187]: https://github.com/ashleygwilliams/wasm-pack/pull/187\n\n- **wasm category for crates.io discovery- [TomasHubelbauer], [pull/149]**\n\n [crates.io] has [categories] to help folks discover crates, be we weren't\n leveraging it! Now- if you explore the [`wasm` category] on [crates.io]\n you'll see `wasm-pack`!\n\n[crates.io]: https://crates.io/\n[categories]: https://crates.io/categories\n[`wasm` category]: https://crates.io/categories/wasm\n[TomasHubelbauer]: https://github.com/TomasHubelbauer\n[pull/149]: https://github.com/ashleygwilliams/wasm-pack/pull/149\n\n- **human panic is now 1.0.0 - [spacekookie], [pull/156]**\n\n Congrats friends! We like what you do.\n\n[pull/156]: https://github.com/ashleygwilliams/wasm-pack/pull/156\n[spacekookie]: https://github.com/spacekookie\n\n### šŸ“– Documentation\n\n- **cleaned up the README - [ashleygwilliams], [pull/155]**\n\n Our `README` was struggling with a common problem- doing too much at once.\n More specifically, it wasn't clear who the audience was, contributers or\n end users? We've cleaned up our README and created a document specifically\n to help contributors get up and running.\n\n[pull/155]: https://github.com/ashleygwilliams/wasm-pack/pull/155\n\n## šŸŒ  0.3.1\n\nBabby's first point release! Are we a real project now?\n\n### šŸ¤• Fixes\n\n- **fixed `init` `Is a Directory` error - [ashleygwilliams], [pull/139]**\n\n Our new logging feature accidentally introduced a regression into 0.3.0. When\n calling `wasm-pack init`, if a directory was not passed, a user would receive\n a \"Is a Directory\" Error. Sorry about that! Thanks to [jbolila] for filing\n [issue/136]!\n\n[pull/139]: https://github.com/ashleygwilliams/wasm-pack/pull/139\n[issue/136]: https://github.com/ashleygwilliams/wasm-pack/issues/136\n[jbolila]: https://github.com/jbolila\n\n- **typescript files were not included in published package - [danreeves], [pull/138]**\n\n Generating Typescript type files by default was a pretty rad feature in\n 0.3.0 but we accidentally forgot to ensure they were included in the\n published package. Thanks so much to [danreeves] for catching this issue\n and fixing it for us!\n\n[danreeves]: https://github.com/danreeves\n[pull/138]: https://github.com/ashleygwilliams/wasm-pack/pull/138\n\n## šŸ’« 0.3.0\n\n### āœØ Features\n\n- **Logging - [mgattozzi], [pull/134]**\n\n Up until now, we've forced folks to rely on emoji-jammed console output to debug\n errors. While emojis are fun, this is often not the most pleasant experience. Now\n we'll generate a `wasm-pack.log` file if `wasm-pack` errors on you, and you can\n customize the log verbosity using the (previously unimplemented) verbosity flag.\n\n[pull/134]: https://github.com/ashleygwilliams/wasm-pack/pull/134\n\n- **`--target` flag - [djfarly], [pull/132]**\n\n `wasm-bindgen-cli` is able to generate a JS module wrapper for generated wasm files\n for both ES6 modules and CommonJS. Up until now, we only used wasm-bindgen's default\n behavior, ES6 modules. You can now pass a `--target` flag with either `nodejs` or\n `browser` to generate the type of module you want to use. Defaults to `browser` if not\n passed.\n\n[djfarly]: https://github.com/djfarly\n[pull/132]: https://github.com/ashleygwilliams/wasm-pack/pull/132\n\n- **human readable panics - [yoshuawuyts], [pull/118]**\n\n Panics aren't always the most friendly situation ever. While we never want to panic on ya,\n if we do- we'll do it in a way that's a little more readable now.\n\n[pull/118]: https://github.com/ashleygwilliams/wasm-pack/pull/118\n\n- **typescript support by default - [kwonoj], [pull/109]**\n\n `wasm-bindgen` now generates typescript type files by default. To suppress generating\n the type file you can pass the `--no-typescript` flag. The type file is useful for more\n than just typescript folks- many IDEs use it for completion!\n\n[kwonoj]: https://github.com/kwonoj\n[pull/109]: https://github.com/ashleygwilliams/wasm-pack/pull/109\n\n- **wrap `npm login` command - [djfarly], [pull/100]**\n\n In order to publish a package to npm, you need to be logged in. You can now use\n `wasm-pack login` to login to the npm (or any other) registry.\n\n[pull/100]: https://github.com/ashleygwilliams/wasm-pack/pull/100\n\n- **exit early on failure - [mgattozzi], [pull/90]**\n\n Until now, `wasm-pack` would continue to run tasks, even if a task failed. Now- if something\n fails, we'll exit so you don't have to wait to fix the error.\n\n[pull/90]: https://github.com/ashleygwilliams/wasm-pack/pull/90\n\n### šŸ¤• Fixes\n\n- **force install wasm-bindgen - [ashleygwilliams], [pull/133]**\n\n Using an out of date version of `wasm-bindgen` can run you into a bunch of trouble. This\n very small change should fix the large number of bug reports we received from users using\n an out of date `wasm-bindgen-cli` by force installing `wasm-bindgen-cli` to ensure the user\n always has the latest version. We don't expect this to be a forever solution (it's a bit\n slow!) but it should help those who are getting started have a less rough time.\n\n[pull/133]: https://github.com/ashleygwilliams/wasm-pack/pull/133\n\n- **fix CI release builds - [ashleygwilliams], [pull/135]**\n\n This was not working! But now it is! You can always use `cargo install` to install\n wasm-pack, but now you can find pre-built Linux and Mac binaries in the [Releases]\n tab of our GitHub repo.\n\n[Releases]: https://github.com/ashleygwilliams/wasm-pack/releases\n[pull/135]: https://github.com/ashleygwilliams/wasm-pack/pull/135\n\n### šŸ› ļø Maintenance\n\n- **remove `quicli` dependency - [mgattozzi], [pull/131]**\n\n While `quicli` is a great way to get started writing a CLI app in Rust- it's not meant for\n large, mature applications. Now that `wasm-pack` is bigger and has many active users, we've\n removed this dependency to unblock further development on the tool.\n\n[pull/131]: https://github.com/ashleygwilliams/wasm-pack/pull/131\n\n- **update rustfmt CI test - [djfarly], [pull/128]**\n\n Since 0.2.0 how one should call `rustfmt` changed! We've kept it up to date so we can continue\n to maintain conventional style in the codebase.\n\n[pull/128]: https://github.com/ashleygwilliams/wasm-pack/pull/128\n\n- **custom module for errors - [mgattozzi], [pull/120]**\n\n Thanks to the `failure` crate, we've been playing fast and loose with errors for a bit. We're\n finally getting serious about error handling - by organizing all of our specific errors in a\n specific module. This will make it easier to communicate these errors out and handle new error\n cases from future features.\n\n[pull/120]: https://github.com/ashleygwilliams/wasm-pack/pull/120\n\n### šŸ“– Documentation\n\nSpecial thanks to [data-pup] who continues to be our documentation champion! In case you missed it,\ncheck out the guides in the [docs directory!](docs)!\n\n## šŸŒŒ 0.2.0\n\nThis release focuses on filling out all commands and improving stderr/out\nhandling for improved user experience!\n\n### āœØ Features\n\n- **`pack` and `publish` - [jamiebuilds], [pull/67]**\n You can now run `wasm-pack pack` to generate a tarball of your generated package,\n as well as run `wasm-pack publish` to publish your package to the npm registry.\n Both commands require that you have npm installed, and the `publish` command requires\n that you be logged in to the npm client. We're working on wrapping the `npm login`\n command so that you can also login directly from `wasm-pack`, see [pull/100] for more\n details.\n\n[jamiebuilds]: https://github.com/jamiebuilds\n[pull/67]: https://github.com/ashleygwilliams/wasm-pack/pull/67\n[pull/100]: https://github.com/ashleygwilliams/wasm-pack/pull/100\n\n- **`package.json` is pretty printed now - [yoshuawuyts], [pull/70]**\n\n Previously, `package.json` was not very human readable. Now it is pretty printed!\n\n- **`collaborators` - [yoshuawuyts], [pull/70]**\n\n `wasm-pack` now will fill out the `collaborators` field in your `package.json` for\n you based on your `Cargo.toml` `authors` data. For more discussion on how we decided\n on this v.s. other types of `author` fields in `package.json`, see [issues/2].\n\n[yoshuawuyts]: https://github.com/yoshuawuyts\n[pull/70]: https://github.com/ashleygwilliams/wasm-pack/pull/70\n[issues/2]: https://github.com/ashleygwilliams/wasm-pack/issues/2\n\n- **Release binaries built with CI - [ashleygwilliams], [pull/103]**\n\n[ashleygwilliams]: https://github.com/ashleygwilliams\n[pull/103]: https://github.com/ashleygwilliams/wasm-pack/pull/103\n\n### šŸ¤• Fixes\n\n- **Optional `package.json` fields warn instead of failing - [mgattozzi], [pull/65]**\n\n[pull/65]: https://github.com/ashleygwilliams/wasm-pack/pull/65\n\n- **Program doesn't swallow stout and sterr - [mgattozzi], [pull/90]**\n\n[mgattozzi]: https://github.com/mgattozzi\n[pull/90]: https://github.com/ashleygwilliams/wasm-pack/pull/90\n\n### šŸ› ļø Maintenance and šŸ“– Documentation\n\nThanks so much to [mgattozzi], [data-pup], [sendilkumarn], [Andy-Bell],\n[steveklabnik], [jasondavies], and [edsrzf] for all the awesome refactoring,\ndocumentation, typo-fixing, and testing work. We appreciate it so much!\n\n[data-pup]: https://github.com/data-pup\n[sendilkumarn]: https://github.com/sendilkumarn\n[Andy-Bell]: https://github.com/Andy-Bell\n[steveklabnik]: https://github.com/steveklabnik\n[jasondavies]: https://github.com/jasondavies\n[edsrzf]: https://github.com/edsrzf\n\n## šŸ’„ 0.1.0\n\n- First release!\n" }, { "path": "CODE_OF_CONDUCT.md", "content": "# The Rust Code of Conduct\n\nA version of this document [can be found online](https://www.rust-lang.org/conduct.html).\n\n## Conduct\n\n**Contact**: [rust-mods@rust-lang.org](mailto:rust-mods@rust-lang.org)\n\n* We are committed to providing a friendly, safe and welcoming environment for all, regardless of level of experience, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, or other similar characteristic.\n* On IRC, please avoid using overtly sexual nicknames or other nicknames that might detract from a friendly, safe and welcoming environment for all.\n* Please be kind and courteous. There's no need to be mean or rude.\n* Respect that people have differences of opinion and that every design or implementation choice carries a trade-off and numerous costs. There is seldom a right answer.\n* Please keep unstructured critique to a minimum. If you have solid ideas you want to experiment with, make a fork and see how it works.\n* We will exclude you from interaction if you insult, demean or harass anyone. That is not welcome behavior. We interpret the term \"harassment\" as including the definition in the Citizen Code of Conduct; if you have any lack of clarity about what might be included in that concept, please read their definition. In particular, we don't tolerate behavior that excludes people in socially marginalized groups.\n* Private harassment is also unacceptable. No matter who you are, if you feel you have been or are being harassed or made uncomfortable by a community member, please contact one of the channel ops or any of the [Rust moderation team][mod_team] immediately. Whether you're a regular contributor or a newcomer, we care about making this community a safe place for you and we've got your back.\n* Likewise any spamming, trolling, flaming, baiting or other attention-stealing behavior is not welcome.\n\n## Moderation\n\n\nThese are the policies for upholding our community's standards of conduct. If you feel that a thread needs moderation, please contact the [Rust moderation team][mod_team].\n\n1. Remarks that violate the Rust standards of conduct, including hateful, hurtful, oppressive, or exclusionary remarks, are not allowed. (Cursing is allowed, but never targeting another user, and never in a hateful manner.)\n2. Remarks that moderators find inappropriate, whether listed in the code of conduct or not, are also not allowed.\n3. Moderators will first respond to such remarks with a warning.\n4. If the warning is unheeded, the user will be \"kicked,\" i.e., kicked out of the communication channel to cool off.\n5. If the user comes back and continues to make trouble, they will be banned, i.e., indefinitely excluded.\n6. Moderators may choose at their discretion to un-ban the user if it was a first offense and they offer the offended party a genuine apology.\n7. If a moderator bans someone and you think it was unjustified, please take it up with that moderator, or with a different moderator, **in private**. Complaints about bans in-channel are not allowed.\n8. Moderators are held to a higher standard than other community members. If a moderator creates an inappropriate situation, they should expect less leeway than others.\n\nIn the Rust community we strive to go the extra step to look out for each other. Don't just aim to be technically unimpeachable, try to be your best self. In particular, avoid flirting with offensive or sensitive issues, particularly if they're off-topic; this all too often leads to unnecessary fights, hurt feelings, and damaged trust; worse, it can drive people away from the community entirely.\n\nAnd if someone takes issue with something you said or did, resist the urge to be defensive. Just stop doing what it was they complained about and apologize. Even if you feel you were misinterpreted or unfairly accused, chances are good there was something you could've communicated better ā€” remember that it's your responsibility to make your fellow Rustaceans comfortable. Everyone wants to get along and we are all here first and foremost because we want to talk about cool technology. You will find that people will be eager to assume good intent and forgive as long as you earn their trust.\n\nThe enforcement policies listed above apply to all official Rust venues; including official IRC channels (#rust, #rust-internals, #rust-tools, #rust-libs, #rustc, #rust-beginners, #rust-docs, #rust-community, #rust-lang, and #cargo); GitHub repositories under rust-lang, rust-lang-nursery, and rust-lang-deprecated; and all forums under rust-lang.org (users.rust-lang.org, internals.rust-lang.org). For other projects adopting the Rust Code of Conduct, please contact the maintainers of those projects for enforcement. If you wish to use this code of conduct for your own project, consider explicitly mentioning your moderation policy or making a copy with your own moderation policy so as to avoid confusion.\n\n*Adapted from the [Node.js Policy on Trolling](http://blog.izs.me/post/30036893703/policy-on-trolling) as well as the [Contributor Covenant v1.3.0](https://www.contributor-covenant.org/version/1/3/0/).*\n\n[mod_team]: https://www.rust-lang.org/team.html#Moderation-team\n" }, { "path": "CONTRIBUTING.md", "content": "# Contributing\n\n## Filing an Issue\n\nIf you are trying to use `wasm-pack` and run into an issue- please file an\nissue! We'd love to get you up and running, even if the issue you have might\nnot be directly related to the code in `wasm-pack`. This tool seeks to make\nit easy for developers to get going, so there's a good chance we can do\nsomething to alleviate the issue by making `wasm-pack` better documented or\nmore robust to different developer environments.\n\nWhen filing an issue, do your best to be as specific as possible. Include\nthe version of rust you are using (`rustc --version`) and your operating\nsystem and version. The faster was can reproduce your issue, the faster we\ncan fix it for you!\n\n## Submitting a PR\n\nIf you are considering filing a pull request, make sure that there's an issue\nfiled for the work you'd like to do. There might be some discussion required!\nFiling an issue first will help ensure that the work you put into your pull\nrequest will get merged :)\n\nBefore you submit your pull request, check that you have completed all of the\nsteps mentioned in the pull request template. Link the issue that your pull\nrequest is responding to, and format your code using [rustfmt][rustfmt].\n\n### Configuring rustfmt\n\nBefore submitting code in a PR, make sure that you have formatted the codebase\nusing [rustfmt][rustfmt]. `rustfmt` is a tool for formatting Rust code, which\nhelps keep style consistent across the project. If you have not used `rustfmt`\nbefore, it is not too difficult.\n\nIf you have not already configured `rustfmt` for the\nnightly toolchain, it can be done using the following steps:\n\n**1. Use Nightly Toolchain**\n\nUse the `rustup override` command to make sure that you are using the nightly\ntoolchain. Run this command in the `wasm-pack` directory you cloned.\n\n```sh\nrustup override set nightly\n```\n\n**2. Add the rustfmt component**\n\nInstall the most recent version of `rustfmt` using this command:\n\n```sh\nrustup component add rustfmt-preview --toolchain nightly\n```\n\n**3. Running rustfmt**\n\nTo run `rustfmt`, use this command:\n\n```sh\ncargo +nightly fmt\n```\n\n[rustfmt]: https://github.com/rust-lang-nursery/rustfmt\n\n### IDE Configuration files\nMachine specific configuration files may be generaged by your IDE while working on the project. Please make sure to add these files to a global .gitignore so they are kept from accidentally being commited to the project and causing issues for other contributors.\n\nSome examples of these files are the `.idea` folder created by JetBrains products (WebStorm, IntelliJ, etc) as well as `.vscode` created by Visual Studio Code for workspace specific settings. \n\nFor help setting up a global .gitignore check out this [GitHub article]!\n\n[GitHub article]: https://help.github.com/articles/ignoring-files/#create-a-global-gitignore\n\n## Running tests\n\nSome of this project's tests run in the browser with webdriver. macOS users\nmay need to first run:\n\n```\nsafaridriver --enable\n```\n\n## Conduct\n\nAs mentioned in the readme file, this project is a part of the [`rust-wasm` working group],\nan official working group of the Rust project. We follow the Rust [Code of Conduct and enforcement policies].\n\n[`rust-wasm` working group]: https://github.com/rustwasm/team\n[Code of Conduct and enforcement policies]: CODE_OF_CONDUCT.md\n" }, { "path": "Cargo.toml", "content": "[package]\nname = \"wasm-pack\"\ndescription = \"šŸ“¦āœØ your favorite rust -> wasm workflow tool!\"\nversion = \"0.14.0\"\nauthors = [\"Ashley Williams \", \"Jesper HĆ„kansson \"]\nrepository = \"https://github.com/drager/wasm-pack.git\"\nlicense = \"MIT OR Apache-2.0\"\nedition = \"2021\"\nreadme = \"README.md\"\ncategories = [\"wasm\"]\ndocumentation = \"https://drager.github.io/wasm-pack/\"\n\n[dependencies]\nanyhow = \"1.0.100\"\nbinary-install = \"0.4.1\"\ncargo_metadata = \"0.23.1\"\nchrono = \"0.4.42\"\nconsole = \"0.16.1\"\ndialoguer = \"0.12.0\"\nenv_logger = { version = \"0.11.8\", default-features = false }\nglob = \"0.3.3\"\nhuman-panic = \"2.0.4\"\nlog = \"0.4.28\"\nparking_lot = \"0.12.5\"\nsemver = \"1.0.27\"\nserde = \"1.0.228\"\nserde_derive = \"1.0.228\"\nserde_ignored = \"0.1.14\"\nserde_json = \"1.0.145\"\nsiphasher = \"1.0.1\"\nstrsim = \"0.11.1\"\nclap = { version = \"4.2.5\", features = [\"derive\"] }\ntoml = \"0.9.8\"\nureq = { version = \"2.12.1\", features = [\"json\", \"socks-proxy\"] }\nwalkdir = \"2.5.0\"\nwhich = \"8.0.0\"\npath-clean = \"1.0.1\"\n\n[dev-dependencies]\nassert_cmd = \"2.1.1\"\nlazy_static = \"1.5.0\"\npredicates = \"3.1.3\"\nserial_test = \"3.2.0\"\ntempfile = \"3.23.0\"\n\n" }, { "path": "LICENSE-APACHE", "content": " Apache License\n Version 2.0, January 2004\n http://www.apache.org/licenses/\n\nTERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION\n\n1. Definitions.\n\n \"License\" shall mean the terms and conditions for use, reproduction,\n and distribution as defined by Sections 1 through 9 of this document.\n\n \"Licensor\" shall mean the copyright owner or entity authorized by\n the copyright owner that is granting the License.\n\n \"Legal Entity\" shall mean the union of the acting entity and all\n other entities that control, are controlled by, or are under common\n control with that entity. For the purposes of this definition,\n \"control\" means (i) the power, direct or indirect, to cause the\n direction or management of such entity, whether by contract or\n otherwise, or (ii) ownership of fifty percent (50%) or more of the\n outstanding shares, or (iii) beneficial ownership of such entity.\n\n \"You\" (or \"Your\") shall mean an individual or Legal Entity\n exercising permissions granted by this License.\n\n \"Source\" form shall mean the preferred form for making modifications,\n including but not limited to software source code, documentation\n source, and configuration files.\n\n \"Object\" form shall mean any form resulting from mechanical\n transformation or translation of a Source form, including but\n not limited to compiled object code, generated documentation,\n and conversions to other media types.\n\n \"Work\" shall mean the work of authorship, whether in Source or\n Object form, made available under the License, as indicated by a\n copyright notice that is included in or attached to the work\n (an example is provided in the Appendix below).\n\n \"Derivative Works\" shall mean any work, whether in Source or Object\n form, that is based on (or derived from) the Work and for which the\n editorial revisions, annotations, elaborations, or other modifications\n represent, as a whole, an original work of authorship. For the purposes\n of this License, Derivative Works shall not include works that remain\n separable from, or merely link (or bind by name) to the interfaces of,\n the Work and Derivative Works thereof.\n\n \"Contribution\" shall mean any work of authorship, including\n the original version of the Work and any modifications or additions\n to that Work or Derivative Works thereof, that is intentionally\n submitted to Licensor for inclusion in the Work by the copyright owner\n or by an individual or Legal Entity authorized to submit on behalf of\n the copyright owner. For the purposes of this definition, \"submitted\"\n means any form of electronic, verbal, or written communication sent\n to the Licensor or its representatives, including but not limited to\n communication on electronic mailing lists, source code control systems,\n and issue tracking systems that are managed by, or on behalf of, the\n Licensor for the purpose of discussing and improving the Work, but\n excluding communication that is conspicuously marked or otherwise\n designated in writing by the copyright owner as \"Not a Contribution.\"\n\n \"Contributor\" shall mean Licensor and any individual or Legal Entity\n on behalf of whom a Contribution has been received by Licensor and\n subsequently incorporated within the Work.\n\n2. Grant of Copyright License. Subject to the terms and conditions of\n this License, each Contributor hereby grants to You a perpetual,\n worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n copyright license to reproduce, prepare Derivative Works of,\n publicly display, publicly perform, sublicense, and distribute the\n Work and such Derivative Works in Source or Object form.\n\n3. Grant of Patent License. Subject to the terms and conditions of\n this License, each Contributor hereby grants to You a perpetual,\n worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n (except as stated in this section) patent license to make, have made,\n use, offer to sell, sell, import, and otherwise transfer the Work,\n where such license applies only to those patent claims licensable\n by such Contributor that are necessarily infringed by their\n Contribution(s) alone or by combination of their Contribution(s)\n with the Work to which such Contribution(s) was submitted. If You\n institute patent litigation against any entity (including a\n cross-claim or counterclaim in a lawsuit) alleging that the Work\n or a Contribution incorporated within the Work constitutes direct\n or contributory patent infringement, then any patent licenses\n granted to You under this License for that Work shall terminate\n as of the date such litigation is filed.\n\n4. Redistribution. You may reproduce and distribute copies of the\n Work or Derivative Works thereof in any medium, with or without\n modifications, and in Source or Object form, provided that You\n meet the following conditions:\n\n (a) You must give any other recipients of the Work or\n Derivative Works a copy of this License; and\n\n (b) You must cause any modified files to carry prominent notices\n stating that You changed the files; and\n\n (c) You must retain, in the Source form of any Derivative Works\n that You distribute, all copyright, patent, trademark, and\n attribution notices from the Source form of the Work,\n excluding those notices that do not pertain to any part of\n the Derivative Works; and\n\n (d) If the Work includes a \"NOTICE\" text file as part of its\n distribution, then any Derivative Works that You distribute must\n include a readable copy of the attribution notices contained\n within such NOTICE file, excluding those notices that do not\n pertain to any part of the Derivative Works, in at least one\n of the following places: within a NOTICE text file distributed\n as part of the Derivative Works; within the Source form or\n documentation, if provided along with the Derivative Works; or,\n within a display generated by the Derivative Works, if and\n wherever such third-party notices normally appear. The contents\n of the NOTICE file are for informational purposes only and\n do not modify the License. You may add Your own attribution\n notices within Derivative Works that You distribute, alongside\n or as an addendum to the NOTICE text from the Work, provided\n that such additional attribution notices cannot be construed\n as modifying the License.\n\n You may add Your own copyright statement to Your modifications and\n may provide additional or different license terms and conditions\n for use, reproduction, or distribution of Your modifications, or\n for any such Derivative Works as a whole, provided Your use,\n reproduction, and distribution of the Work otherwise complies with\n the conditions stated in this License.\n\n5. Submission of Contributions. Unless You explicitly state otherwise,\n any Contribution intentionally submitted for inclusion in the Work\n by You to the Licensor shall be under the terms and conditions of\n this License, without any additional terms or conditions.\n Notwithstanding the above, nothing herein shall supersede or modify\n the terms of any separate license agreement you may have executed\n with Licensor regarding such Contributions.\n\n6. Trademarks. This License does not grant permission to use the trade\n names, trademarks, service marks, or product names of the Licensor,\n except as required for reasonable and customary use in describing the\n origin of the Work and reproducing the content of the NOTICE file.\n\n7. Disclaimer of Warranty. Unless required by applicable law or\n agreed to in writing, Licensor provides the Work (and each\n Contributor provides its Contributions) on an \"AS IS\" BASIS,\n WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or\n implied, including, without limitation, any warranties or conditions\n of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A\n PARTICULAR PURPOSE. You are solely responsible for determining the\n appropriateness of using or redistributing the Work and assume any\n risks associated with Your exercise of permissions under this License.\n\n8. Limitation of Liability. In no event and under no legal theory,\n whether in tort (including negligence), contract, or otherwise,\n unless required by applicable law (such as deliberate and grossly\n negligent acts) or agreed to in writing, shall any Contributor be\n liable to You for damages, including any direct, indirect, special,\n incidental, or consequential damages of any character arising as a\n result of this License or out of the use or inability to use the\n Work (including but not limited to damages for loss of goodwill,\n work stoppage, computer failure or malfunction, or any and all\n other commercial damages or losses), even if such Contributor\n has been advised of the possibility of such damages.\n\n9. Accepting Warranty or Additional Liability. While redistributing\n the Work or Derivative Works thereof, You may choose to offer,\n and charge a fee for, acceptance of support, warranty, indemnity,\n or other liability obligations and/or rights consistent with this\n License. However, in accepting such obligations, You may act only\n on Your own behalf and on Your sole responsibility, not on behalf\n of any other Contributor, and only if You agree to indemnify,\n defend, and hold each Contributor harmless for any liability\n incurred by, or claims asserted against, such Contributor by reason\n of your accepting any such warranty or additional liability.\n\nEND OF TERMS AND CONDITIONS\n\nAPPENDIX: How to apply the Apache License to your work.\n\n To apply the Apache License to your work, attach the following\n boilerplate notice, with the fields enclosed by brackets \"[]\"\n replaced with your own identifying information. (Don't include\n the brackets!) The text should be enclosed in the appropriate\n comment syntax for the file format. We also recommend that a\n file or class name and description of purpose be included on the\n same \"printed page\" as the copyright notice for easier\n identification within third-party archives.\n\nCopyright [yyyy] [name of copyright owner]\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n" }, { "path": "LICENSE-MIT", "content": "Copyright (c) 2018 Ashley Williams\n\nPermission is hereby granted, free of charge, to any\nperson obtaining a copy of this software and associated\ndocumentation files (the \"Software\"), to deal in the\nSoftware without restriction, including without\nlimitation the rights to use, copy, modify, merge,\npublish, distribute, sublicense, and/or sell copies of\nthe Software, and to permit persons to whom the Software\nis furnished to do so, subject to the following\nconditions:\n\nThe above copyright notice and this permission notice\nshall be included in all copies or substantial portions\nof the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF\nANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED\nTO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A\nPARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT\nSHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY\nCLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION\nOF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR\nIN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER\nDEALINGS IN THE SOFTWARE.\n" }, { "path": "README.md", "content": "
\n\n

šŸ“¦āœØ wasm-pack

\n\n

\n Your favorite Rust ā†’ Wasm workflow tool!\n

\n\n

\n \"Build\n \"crates.io\"\n

\n\n

\n Docs\n | \n Contributing\n | \n Chat\n

\n\n\n
\n\n## About\n\nThis tool seeks to be a one-stop shop for building and working with rust-\ngenerated WebAssembly that you would like to interop with JavaScript, in the\nbrowser or with Node.js. `wasm-pack` helps you build rust-generated\nWebAssembly packages that you could publish to the npm registry, or otherwise use\nalongside any javascript packages in workflows that you already use, such as [webpack].\n\n[webpack]: https://webpack.js.org/\n\n![demo](demo.gif)\n\n## šŸ”® Prerequisites\n\nThis project requires Rust 1.30.0 or later.\n\n- [Development Environment](https://drager.github.io/wasm-pack/book/prerequisites/index.html)\n- [Installation](https://drager.github.io/wasm-pack/installer)\n\n## āš” Quickstart Guide\n\nVisit the [quickstart guide] in our documentation.\n\n[quickstart guide]: https://drager.github.io/wasm-pack/book/quickstart.html\n\n## šŸŽ™ļø Commands\n\n- [`new`](https://drager.github.io/wasm-pack/book/commands/new.html): Generate a new RustWasm project using a template\n- [`build`](https://drager.github.io/wasm-pack/book/commands/build.html): Generate an npm wasm pkg from a rustwasm crate\n- [`test`](https://drager.github.io/wasm-pack/book/commands/test.html): Run browser tests\n- [`pack` and `publish`](https://drager.github.io/wasm-pack/book/commands/pack-and-publish.html): Create a tarball of your rustwasm pkg and/or publish to a registry\n\n## šŸ“ Logging\n\n`wasm-pack` uses [`env_logger`] to produce logs when `wasm-pack` runs.\n\nTo configure your log level, use the `RUST_LOG` environment variable. For example:\n\n```\nRUST_LOG=info wasm-pack build\n```\n\n[`env_logger`]: https://crates.io/crates/env_logger\n\n## šŸ‘Æ Contributing\n\nRead our [guide] on getting up and running for developing `wasm-pack`, and\ncheck out our [contribution policy].\n\n[guide]: https://drager.github.io/wasm-pack/book/contributing.html\n[contribution policy]: CONTRIBUTING.md\n\n## šŸ¤¹ā€ā™€ļø Governance\n\nThis project was started by [ashleygwilliams] and is maintained by [drager].\n\n[ashleygwilliams]: https://github.com/ashleygwilliams\n[drager]: https://github.com/drager\n" }, { "path": "RELEASE_CHECKLIST.md", "content": "# Release Checklist\n\nThis is a list of the things that need to happen during a release.\n\n1. Open the associated milestone. All issues and PRs should be closed. If\n they are not you should reassign all open issues and PRs to future\n milestones.\n1. Go through the commit history since last release. Ensure that all PRs\n that have landed are marked with the milestone. You can use this to \n show all the PRs that are merged on or after YYY-MM-DD: \n `https://github.com/issues?utf8=%E2%9C%93&q=repo%3Arustwasm%2Fwasm-pack+merged%3A%3E%3DYYYY-MM-DD`\n1. Go through the closed PRs in the milestone. Each should have a changelog\n label indicating if the change is docs, fix, feature, or maintenance. If\n there is a missing label, please add one.\n1. Choose an emoji for the release. Try to make it some sort of transition\n from the previous releases emoji (point releases can be a little weirder).\n1. Create a new branch \"#.#.#\" where \"#.#.#\" is the release's version.\n1. Add this release to the `CHANGELOG.md`. Use the structure of previous \n entries.\n1. Update `DEFAULT_CHROMEDRIVER_VERSION` in `chromedriver.rs`. \n Version is the response of `https://chromedriver.storage.googleapis.com/LATEST_RELEASE`.\n1. Update `DEFAULT_GECKODRIVER_VERSION` in `geckodriver.rs`.\n Version is the name of the latest tag - `https://github.com/mozilla/geckodriver/releases/latest`.\n1. Update the version in `Cargo.toml`.\n1. Update the version number and date in `docs/index.html`.\n1. Run `cargo update`.\n1. Run `cargo test`.\n1. Run `cargo build`.\n1. Copy `README.md` to `npm/README.md`\n1. Bump the version number in `npm/package.json`\n1. `cd npm && npm install`\n1. Push up a commit with the `Cargo.toml`, `Cargo.lock`, `docs/index.html`,\n and `CHANGELOG.md` changes. The commit message can just be \"#.#.#\".\n1. Request review from `@ashleygwilliams` and `@drager`.\n1. `git commit --amend` all changes into the single commit.\n1. Once ready to merge, tag the commit with the tag `v#.#.#`.\n1. Wait for the CI to go green.\n1. The CI will build the release binaries. Take the `CHANGELOG.md` release\n entry and cut and paste it into the release body.\n1. Be sure to add any missing link definitions to the release.\n1. Hit the big green Merge button.\n1. `git checkout master` and `git pull --rebase origin master`\n1. Run `cargo test`.\n1. `cargo publish`\n1. `cd npm && npm publish`\n1. Tweet.\n" }, { "path": "clippy.toml", "content": "too-many-arguments-threshold = 8" }, { "path": "docs/_installer/build-installer.rs", "content": "use std::fs;\n\nfn main() {\n fs::create_dir_all(\"docs/installer\").unwrap();\n fs::copy(\n \"docs/_installer/wasm-pack.js\",\n \"docs/installer/wasm-pack.js\",\n ).unwrap();\n let index = fs::read_to_string(\"docs/_installer/index.html\").unwrap();\n fs::write(\n \"docs/installer/index.html\",\n fixup(&index),\n ).unwrap();\n\n let init = fs::read_to_string(\"docs/_installer/init.sh\").unwrap();\n fs::write(\n \"docs/installer/init.sh\",\n fixup(&init),\n ).unwrap();\n}\n\nfn fixup(input: &str) -> String {\n let manifest = fs::read_to_string(\"Cargo.toml\").unwrap();\n let version = manifest.lines()\n .find(|line| line.starts_with(\"version =\"))\n .unwrap();\n let version = &version[version.find('\"').unwrap() + 1..version.rfind('\"').unwrap()];\n\n input.replace(\"$VERSION\", &format!(\"v{}\", version))\n}\n" }, { "path": "docs/_installer/index.html", "content": "\n\n \n wasm-pack\n \n \n \n \n \n \n \n \n \n \n\n\n \n
\n \n

Install wasm-pack

\n
\n
\n

\n You appear to be running a *nix system (Unix, Linux, MacOS). Install\n by running:\n

\n 
\ncurl https://drager.github.io/wasm-pack/installer/init.sh -sSf | sh\n        
\n          If you're not on *nix, or you don't like installing from curl,\n          follow the alternate instructions below.\n        
\n
\n\n
\n

\n You appear to be running Windows 64-bit. Download and run\n wasm-pack-init.exe\n then follow the onscreen instructions.\n

\n
\n

\n If you're a Windows Subsystem for Linux user, run the following in\n your terminal, then follow the onscreen instructions to install\n wasm-pack.\n

\n 
\ncurl https://drager.github.io/wasm-pack/installer/init.sh -sSf | sh\n        
\n          If you're not on Windows 64-bit, follow the alternate instructions\n          below.\n        
\n
\n\n \n\n
\n\n
\n

To install from source on any platform:

\n

cargo install wasm-pack

\n

\n On supported platforms, you can also use npm or yarn to\n download a precompiled binary:\n

\n

\n npm install -g wasm-pack or\n yarn global add wasm-pack\n

\n
\n
\n
\n \n\n" }, { "path": "docs/_installer/init.sh", "content": "#!/bin/bash\n# Copyright 2016 The Rust Project Developers. See the COPYRIGHT\n# file at the top-level directory of this distribution and at\n# http://rust-lang.org/COPYRIGHT.\n#\n# Licensed under the Apache License, Version 2.0 or the MIT license\n# , at your\n# option. This file may not be copied, modified, or distributed\n# except according to those terms.\n\n# This is just a little script that can be downloaded from the internet to\n# install wasm-pack. It just does platform detection, downloads the installer\n# and runs it.\n\nset -u\n\n# Parse VERSION from environment or --version argument, default to \"latest\"\nif [ -z \"${VERSION:-}\" ]; then\n VERSION=\"\"\n ORIG_ARGS=(\"$@\")\n \n while [ $# -gt 0 ]; do\n case $1 in\n --version)\n VERSION=\"$2\"\n shift 2\n ;;\n *)\n shift\n ;;\n esac\n done\n \n set -- \"${ORIG_ARGS[@]}\"\n \n if [ -z \"$VERSION\" ]; then\n VERSION=\"latest\"\n fi\nfi\n\n# Resolve \"latest\" to actual version number\nif [ \"$VERSION\" = \"latest\" ]; then\n VERSION=$(curl -s https://api.github.com/repos/drager/wasm-pack/releases/latest | grep '\"tag_name\"' | sed -E 's/.*\"v?([^\"]+)\".*/\\1/')\n if [ -z \"$VERSION\" ]; then\n err \"failed to fetch latest version from GitHub API\"\n fi\nfi\n\n# Normalize version format for download URL\ncase \"$VERSION\" in\n v*) ;;\n *) VERSION=\"v$VERSION\" ;;\nesac\n\nUPDATE_ROOT=\"https://github.com/drager/wasm-pack/releases/download/$VERSION\"\n\nmain() {\n downloader --check\n need_cmd uname\n need_cmd mktemp\n need_cmd chmod\n need_cmd mkdir\n need_cmd rm\n need_cmd rmdir\n need_cmd tar\n need_cmd which\n need_cmd dirname\n\n get_architecture || return 1\n local _arch=\"$RETVAL\"\n assert_nz \"$_arch\" \"arch\"\n\n local _ext=\"\"\n case \"$_arch\" in\n *windows*)\n _ext=\".exe\"\n ;;\n esac\n\n which rustup > /dev/null 2>&1\n need_ok \"failed to find Rust installation, is rustup installed?\"\n local _rustup=$(which rustup)\n local _tardir=\"wasm-pack-$VERSION-${_arch}\"\n local _url=\"$UPDATE_ROOT/${_tardir}.tar.gz\"\n local _dir=\"$(mktemp -d 2>/dev/null || ensure mktemp -d -t wasm-pack)\"\n local _file=\"$_dir/input.tar.gz\"\n local _wasmpack=\"$_dir/wasm-pack$_ext\"\n local _wasmpackinit=\"$_dir/wasm-pack-init$_ext\"\n\n printf '%s\\n' 'info: downloading wasm-pack' 1>&2\n\n ensure mkdir -p \"$_dir\"\n downloader \"$_url\" \"$_file\"\n if [ $? != 0 ]; then\n say \"failed to download $_url\"\n say \"this may be a standard network error, but it may also indicate\"\n say \"that wasm-pack's release process is not working. When in doubt\"\n say \"please feel free to open an issue!\"\n exit 1\n fi\n ensure tar xf \"$_file\" --strip-components 1 -C \"$_dir\"\n mv \"$_wasmpack\" \"$_wasmpackinit\"\n\n # The installer may want to ask for confirmation on stdin for various\n # operations. We were piped through `sh` though so we probably don't have\n # access to a tty naturally. If it looks like we're attached to a terminal\n # (`-t 1`) then pass the tty down to the installer explicitly.\n if [ -t 1 ]; then\n \"$_wasmpackinit\" \"$@\" < /dev/tty\n else\n \"$_wasmpackinit\" \"$@\"\n fi\n\n local _retval=$?\n\n ignore rm -rf \"$_dir\"\n\n return \"$_retval\"\n}\n\nget_architecture() {\n local _ostype=\"$(uname -s)\"\n local _cputype=\"$(uname -m)\"\n\n # This is when installing inside docker, or can be useful to side-step\n # the script's built-in platform detection heuristic (if it drifts again in the future)\n set +u\n if [ -n \"$TARGETOS\" ]; then\n _ostype=\"$TARGETOS\" # probably always linux\n fi\n\n if [ -n \"$TARGETARCH\" ]; then\n _cputype=\"$TARGETARCH\"\n fi\n set -u\n\n\n if [ \"$_ostype\" = Darwin ] && [ \"$_cputype\" = i386 ]; then\n # Darwin `uname -s` lies\n if sysctl hw.optional.x86_64 | grep -q ': 1'; then\n local _cputype=x86_64\n fi\n fi\n\n case \"$_ostype\" in\n Linux | linux)\n local _ostype=unknown-linux-musl\n ;;\n\n Darwin)\n local _ostype=apple-darwin\n ;;\n\n MINGW* | MSYS* | CYGWIN*)\n local _ostype=pc-windows-msvc\n ;;\n\n *)\n err \"no precompiled binaries available for OS: $_ostype\"\n ;;\n esac\n\n case \"$_cputype\" in\n x86_64 | x86-64 | x64 | amd64)\n local _cputype=x86_64\n ;;\n arm64 | aarch64)\n local _cputype=aarch64\n ;;\n *)\n err \"no precompiled binaries available for CPU architecture: $_cputype\"\n\n esac\n\n # See https://github.com/drager/wasm-pack/pull/1088\n if [ \"$_cputype\" = \"aarch64\" ] && [ \"$_ostype\" = \"apple-darwin\" ]; then\n _cputype=\"x86_64\"\n fi\n\n local _arch=\"$_cputype-$_ostype\"\n\n RETVAL=\"$_arch\"\n}\n\nsay() {\n echo \"wasm-pack-init: $1\"\n}\n\nerr() {\n say \"$1\" >&2\n exit 1\n}\n\nneed_cmd() {\n if ! check_cmd \"$1\"\n then err \"need '$1' (command not found)\"\n fi\n}\n\ncheck_cmd() {\n command -v \"$1\" > /dev/null 2>&1\n return $?\n}\n\nneed_ok() {\n if [ $? != 0 ]; then err \"$1\"; fi\n}\n\nassert_nz() {\n if [ -z \"$1\" ]; then err \"assert_nz $2\"; fi\n}\n\n# Run a command that should never fail. If the command fails execution\n# will immediately terminate with an error showing the failing\n# command.\nensure() {\n \"$@\"\n need_ok \"command failed: $*\"\n}\n\n# This is just for indicating that commands' results are being\n# intentionally ignored. Usually, because it's being executed\n# as part of error handling.\nignore() {\n \"$@\"\n}\n\n# This wraps curl or wget. Try curl first, if not installed,\n# use wget instead.\ndownloader() {\n if check_cmd curl\n then _dld=curl\n elif check_cmd wget\n then _dld=wget\n else _dld='curl or wget' # to be used in error message of need_cmd\n fi\n\n if [ \"$1\" = --check ]\n then need_cmd \"$_dld\"\n elif [ \"$_dld\" = curl ]\n then curl -sSfL \"$1\" -o \"$2\"\n elif [ \"$_dld\" = wget ]\n then wget \"$1\" -O \"$2\"\n else err \"Unknown downloader\" # should not reach here\n fi\n}\n\nmain \"$@\" || exit 1\n" }, { "path": "docs/_installer/wasm-pack.js", "content": "var platforms = [\"unknown\", \"win64\", \"unix\"];\nvar platform_override = null;\n\nfunction detect_platform() {\n \"use strict\";\n\n if (platform_override !== null) {\n return platforms[platform_override];\n }\n\n var os = \"unknown\";\n\n if (navigator.platform == \"Linux x86_64\") {os = \"unix\";}\n if (navigator.platform == \"Linux i686\") {os = \"unix\";}\n if (navigator.platform == \"Linux i686 on x86_64\") {os = \"unix\";}\n if (navigator.platform == \"Linux aarch64\") {os = \"unix\";}\n if (navigator.platform == \"Linux armv6l\") {os = \"unix\";}\n if (navigator.platform == \"Linux armv7l\") {os = \"unix\";}\n if (navigator.platform == \"Linux armv8l\") {os = \"unix\";}\n if (navigator.platform == \"Linux ppc64\") {os = \"unix\";}\n if (navigator.platform == \"Linux mips\") {os = \"unix\";}\n if (navigator.platform == \"Linux mips64\") {os = \"unix\";}\n if (navigator.platform == \"Mac\") {os = \"unix\";}\n // if (navigator.platform == \"Win32\") {os = \"win32\";}\n if (navigator.platform == \"Win64\" ||\n navigator.userAgent.indexOf(\"WOW64\") != -1 ||\n navigator.userAgent.indexOf(\"Win64\") != -1) { os = \"win64\"; }\n if (navigator.platform == \"FreeBSD x86_64\") {os = \"unix\";}\n if (navigator.platform == \"FreeBSD amd64\") {os = \"unix\";}\n if (navigator.platform == \"NetBSD x86_64\") {os = \"unix\";}\n if (navigator.platform == \"NetBSD amd64\") {os = \"unix\";}\n\n // I wish I knew by now, but I don't. Try harder.\n if (os == \"unknown\") {\n // if (navigator.appVersion.indexOf(\"Win\")!=-1) {os = \"win32\";}\n if (navigator.appVersion.indexOf(\"Mac\")!=-1) {os = \"unix\";}\n // rust-www/#692 - FreeBSD epiphany!\n if (navigator.appVersion.indexOf(\"FreeBSD\")!=-1) {os = \"unix\";}\n }\n\n // Firefox Quantum likes to hide platform and appVersion but oscpu works\n if (navigator.oscpu) {\n // if (navigator.oscpu.indexOf(\"Win32\")!=-1) {os = \"win32\";}\n if (navigator.oscpu.indexOf(\"Win64\")!=-1) {os = \"win64\";}\n if (navigator.oscpu.indexOf(\"Mac\")!=-1) {os = \"unix\";}\n if (navigator.oscpu.indexOf(\"Linux\")!=-1) {os = \"unix\";}\n if (navigator.oscpu.indexOf(\"FreeBSD\")!=-1) {os = \"unix\";}\n if (navigator.oscpu.indexOf(\"NetBSD\")!=-1) {os = \"unix\";}\n }\n\n return os;\n}\n\nfunction adjust_for_platform() {\n \"use strict\";\n\n var platform = detect_platform();\n\n platforms.forEach(function (platform_elem) {\n var platform_div = document.getElementById(\"platform-instructions-\" + platform_elem);\n platform_div.style.display = \"none\";\n if (platform === platform_elem) {\n platform_div.style.display = \"block\";\n }\n });\n}\n\nfunction fill_in_bug_report_values() {\n var nav_plat = document.getElementById(\"nav-plat\");\n var nav_app = document.getElementById(\"nav-app\");\n nav_plat.textContent = navigator.platform;\n nav_app.textContent = navigator.appVersion;\n}\n\n(function () {\n adjust_for_platform();\n fill_in_bug_report_values();\n}());\n" }, { "path": "docs/_theme/header.hbs", "content": "\n
\n

\n This is the unpublished documentation of\n wasm-pack, the published documentation is available\n \n on the main Rust and WebAssembly documentation site\n . Features documented here may not be available in released versions of\n wasm-pack.\n

\n
\n" }, { "path": "docs/book.toml", "content": "[book]\nauthors = [\"Ashley Williams\"]\nsrc = \"src\"\ntitle = \"Hello wasm-pack!\"\n" }, { "path": "docs/browserconfig.xml", "content": "\n\n \n \n \n #00aba9\n \n \n\n" }, { "path": "docs/index.html", "content": "\n\n \n wasm-pack\n \n \n \n \n \n \n \n \n \n\n\n \n
\n
\n
\n
\n \n

wasm-pack

\n

šŸ“¦āœØ your favorite rust -> wasm workflow tool!

\n
\n \n
\n
\n \n\n\n\n" }, { "path": "docs/public/custom.css", "content": "@import url('https://fonts.googleapis.com/css?family=Raleway');\n\n.navbar {\n display: block;\n width: 100%;\n height: 6.5rem;\n background: #fff;\n z-index: 99;\n border-bottom: 1px solid #eee;\n}\n\n.navbar-list {\n list-style: none;\n margin-bottom: 0;\n}\n\n.navbar-item {\n position: relative;\n float: right;\n margin-bottom: 0;\n}\n\n.navbar-logo {\n position: relative;\n float: left;\n margin-bottom: 0;\n bottom: -5px;\n}\n\n.navbar-logo a img {\n width: 50px;\n}\n\n.navbar-item a {\n text-transform: uppercase;\n font-size: 11px;\n font-weight: 600;\n letter-spacing: .2rem;\n margin-right: 35px;\n text-decoration: none;\n line-height: 6.5rem;\n color: #222;\n}\n\n#logo, #installer {\n text-align: center;\n}\n\n#logo {\n padding: 50px;\n}\n\n#logo img {\n width: 80%;\n}\n\n#logo h1, h2 {\n text-align: center;\n}\n\n#logo h2 {\n font-size: 1.8rem;\n letter-spacing: 0.01rem;\n color: #222;\n}\n\n#installer a.button {\n width: 100%;\n height: 20%;\n font-size: 1.8rem;\n padding: 1.8rem;\n margin: 10rem 0 1.8rem 0;\n background-color: #6556EC;\n border-color: #6556EC;\n}\n\n#installer img {\n padding: 50px;\n width: 20%;\n}\n\npre.primary {\n margin: 0 auto 2.5rem auto;\n width: fit-content;\n\n padding: 20px;\n font-size: 2rem;\n background-color: #000;\n color: #fff;\n}\n\na {\n color: #6556EC;\n}\n" }, { "path": "docs/site.webmanifest", "content": "{\n \"name\": \"wasm-pack \",\n \"short_name\": \"wasm-pack \",\n \"icons\": [\n {\n \"src\": \"/android-chrome-192x192.png\",\n \"sizes\": \"192x192\",\n \"type\": \"image/png\"\n },\n {\n \"src\": \"/android-chrome-384x384.png\",\n \"sizes\": \"384x384\",\n \"type\": \"image/png\"\n }\n ],\n \"theme_color\": \"#ffffff\",\n \"background_color\": \"#ffffff\",\n \"display\": \"standalone\"\n}\n" }, { "path": "docs/src/SUMMARY.md", "content": "# Summary\n\n- [Introduction](./introduction.md)\n- [Quickstart](./quickstart.md)\n- [Prerequisites](./prerequisites/index.md)\n - [npm (optional)](./prerequisites/npm.md)\n - [considerations](./prerequisites/considerations.md)\n - [Non-`rustup` setups](./prerequisites/non-rustup-setups.md)\n- [Commands](./commands/index.md)\n - [`new`](./commands/new.md)\n - [`build`](./commands/build.md)\n - [`test`](./commands/test.md)\n - [`pack` and `publish`](./commands/pack-and-publish.md)\n - [`init` (DEPRECATED)](./commands/init.md)\n- [Tutorials](./tutorials/index.md)\n - [Hybrid applications with Webpack](./tutorials/hybrid-applications-with-webpack/index.md)\n - [Getting started](./tutorials/hybrid-applications-with-webpack/getting-started.md)\n - [Using your library](./tutorials/hybrid-applications-with-webpack/using-your-library.md)\n - [npm browser packages](./tutorials/npm-browser-packages/index.md)\n - [Getting started](./tutorials/npm-browser-packages/getting-started.md)\n - [Manual Setup](./tutorials/npm-browser-packages/getting-started/manual-setup.md)\n - [Template deep dive](./tutorials/npm-browser-packages/template-deep-dive/index.md)\n - [`Cargo.toml`](./tutorials/npm-browser-packages/template-deep-dive/cargo-toml.md)\n - [`src/lib.rs`](./tutorials/npm-browser-packages/template-deep-dive/src-lib-rs.md)\n - [`src/utils.rs`](./tutorials/npm-browser-packages/template-deep-dive/src-utils-rs.md)\n - [`wee_alloc`](./tutorials/npm-browser-packages/template-deep-dive/wee_alloc.md)\n - [`tests/web.rs`](./tutorials/npm-browser-packages/template-deep-dive/tests-web-rs.md)\n - [Building your project](./tutorials/npm-browser-packages/building-your-project.md)\n - [Testing your project](./tutorials/npm-browser-packages/testing-your-project.md)\n - [Packaging and publishing](./tutorials/npm-browser-packages/packaging-and-publishing.md)\n - [Using your library](./tutorials/npm-browser-packages/using-your-library.md)\n- [`Cargo.toml` Configuration](./cargo-toml-configuration.md)\n- [Contributing](./contributing.md)\n" }, { "path": "docs/src/cargo-toml-configuration.md", "content": "# `Cargo.toml` Configuration\n\n`wasm-pack` can be configured via the `package.metadata.wasm-pack` key in\n`Cargo.toml`. Every option has a default, and is not required.\n\nThere are three profiles: `dev`, `profiling`, and `release`. These correspond to\nthe `--dev`, `--profiling`, and `--release` flags passed to `wasm-pack build`.\n\nThe available configuration options and their default values are shown below:\n\n```toml\n[package.metadata.wasm-pack.profile.dev]\n# Should `wasm-opt` be used to further optimize the wasm binary generated after\n# the Rust compiler has finished? Using `wasm-opt` can often further decrease\n# binary size or do clever tricks that haven't made their way into LLVM yet.\n#\n# Configuration is set to `false` by default for the dev profile, but it can\n# be set to an array of strings which are explicit arguments to pass to\n# `wasm-opt`. For example `['-Os']` would optimize for size while `['-O4']`\n# would execute very expensive optimizations passes\n#\n# In most cases, the `-O[X]` flag is enough. However, if you require extreme\n# optimizations, see the full list of `wasm-opt` optimization flags\n# https://github.com/WebAssembly/binaryen/blob/version_117/test/lit/help/wasm-opt.test\nwasm-opt = ['-O']\n\n[package.metadata.wasm-pack.profile.dev.wasm-bindgen]\n# Should we enable wasm-bindgen's debug assertions in its generated JS glue?\ndebug-js-glue = true\n# Should wasm-bindgen demangle the symbols in the \"name\" custom section?\ndemangle-name-section = true\n# Should we emit the DWARF debug info custom sections?\ndwarf-debug-info = false\n# Should we omit the default import path?\nomit-default-module-path = false\n# Controls whether wasm-bindgen will split linked modules out into their own files. Enabling this is recommended, because it allows lazy-loading the linked modules and setting a stricter Content Security Policy. Only available in wasm-bindgen 0.2.95 and later.\nsplit-linked-modules = false\n\n[package.metadata.wasm-pack.profile.profiling]\nwasm-opt = ['-O']\n\n[package.metadata.wasm-pack.profile.profiling.wasm-bindgen]\ndebug-js-glue = false\ndemangle-name-section = true\ndwarf-debug-info = false\nomit-default-module-path = false\n\n# `wasm-opt` is on by default in for the release profile, but it can be\n# disabled by setting it to `false`\n[package.metadata.wasm-pack.profile.release]\nwasm-opt = false\n\n[package.metadata.wasm-pack.profile.release.wasm-bindgen]\ndebug-js-glue = false\ndemangle-name-section = true\ndwarf-debug-info = false\nomit-default-module-path = false\n```\n" }, { "path": "docs/src/commands/build.md", "content": "# wasm-pack build\n\nThe `wasm-pack build` command creates the files necessary for JavaScript\ninteroperability and for publishing a package to npm. This involves compiling\nyour code to wasm and generating a pkg folder. This pkg folder will contain the\nwasm binary, a JS wrapper file, your `README`, and a `package.json` file.\n\nThe `pkg` directory is automatically `.gitignore`d by default, since it contains\nbuild artifacts which are not intended to be checked into version\ncontrol.[0](#footnote-0)\n\n## Path\n\nThe `wasm-pack build` command can be given an optional path argument, e.g.:\n\n```\nwasm-pack build examples/js-hello-world\n```\n\nThis path should point to a directory that contains a `Cargo.toml` file. If no\npath is given, the `build` command will run in the current directory.\n\n## Output Directory\n\nBy default, `wasm-pack` will generate a directory for its build output called `pkg`.\nIf you'd like to customize this you can use the `--out-dir` flag.\n\n```\nwasm-pack build --out-dir out\n```\n\nThe above command will put your build artifacts in a directory called `out`, instead\nof the default `pkg`.\n\n## Generated file names\n\nFlag `--out-name` sets the prefix for output file names. If not provided, package name is used instead.\n\nUsage examples, assuming our crate is named `dom`:\n\n```\nwasm-pack build\n# will produce files\n# dom.d.ts dom.js dom_bg.d.ts dom_bg.wasm package.json README.md\n\nwasm-pack build --out-name index\n# will produce files\n# index.d.ts index.js index_bg.d.ts index_bg.wasm package.json README.md\n```\n\n\n## Profile\n\nThe `build` command accepts an optional profile argument: one of `--dev`,\n`--profiling`, or `--release`. If none is supplied, then `--release` is used.\n\nThis controls whether debug assertions are enabled, debug info is generated, and\nwhich (if any) optimizations are enabled.\n\n| Profile | Debug Assertions | Debug Info | Optimizations | Notes |\n|---------------|------------------|------------|---------------|---------------------------------------|\n| `--dev` | Yes | Yes | No | Useful for development and debugging. |\n| `--profiling` | No | Yes | Yes | Useful when profiling and investigating performance issues. |\n| `--release` | No | No | Yes | Useful for shipping to production. |\n\nThe `--dev` profile will build the output package using cargo's [default\nnon-release profile][cargo-profile-sections-documentation]. Building this way is\nfaster but applies few optimizations to the output, and enables debug assertions\nand other runtime correctness checks. The `--profiling` and `--release` profiles\nuse cargo's release profile, but the former enables debug info as well, which\nhelps when investigating performance issues in a profiler.\n\nThe exact meaning of the profile flags may evolve as the platform matures.\n\n[cargo-profile-sections-documentation]: https://doc.rust-lang.org/cargo/reference/manifest.html#the-profile-sections\n\n## Target\n\nThe `build` command accepts a `--target` argument. This will customize the JS\nthat is emitted and how the WebAssembly files are instantiated and loaded. For\nmore documentation on the various strategies here, see the [documentation on\nusing the compiled output][deploy].\n\n```\nwasm-pack build --target nodejs\n```\n\n| Option | Usage | Description |\n|-----------|------------|-----------------------------------------------------------------------------------------------------|\n| *not specified* or `bundler` | [Bundler][bundlers] | Outputs JS that is suitable for interoperation with a Bundler like Webpack. You'll `import` the JS and the `module` key is specified in `package.json`. `sideEffects: false` is by default. |\n| `nodejs` | [Node.js][deploy-nodejs] | Outputs JS that uses CommonJS modules, for use with a `require` statement. `main` key in `package.json`. |\n| `web` | [Native in browser][deploy-web] | Outputs JS that can be natively imported as an ES module in a browser, but the WebAssembly must be manually instantiated and loaded. |\n| `no-modules` | [Native in browser][deploy-web] | Same as `web`, except the JS is included on a page and modifies global state, and doesn't support as many `wasm-bindgen` features as `web` |\n| `deno` | [Deno][deploy-deno] | Outputs JS that can be natively imported as an ES module in deno. |\n\n[deploy]: https://wasm-bindgen.github.io/wasm-bindgen/reference/deployment.html\n[bundlers]: https://wasm-bindgen.github.io/wasm-bindgen/reference/deployment.html#bundlers\n[deploy-nodejs]: https://wasm-bindgen.github.io/wasm-bindgen/reference/deployment.html#nodejs\n[deploy-web]: https://wasm-bindgen.github.io/wasm-bindgen/reference/deployment.html#without-a-bundler\n[deploy-deno]: https://wasm-bindgen.github.io/wasm-bindgen/reference/deployment.html#deno\n\n## Scope\n\nThe `build` command also accepts an optional `--scope` argument. This will scope\nyour package name, which is useful if your package name might conflict with\nsomething in the public registry. For example:\n\n```\nwasm-pack build examples/js-hello-world --scope test\n```\n\nThis command would create a `package.json` file for a package called\n`@test/js-hello-world`. For more information about scoping, you can refer to\nthe npm documentation [here][npm-scope-documentation].\n\n[npm-scope-documentation]: https://docs.npmjs.com/misc/scope\n\n## Mode\n\nThe `build` command accepts an optional `--mode` argument.\n```\nwasm-pack build examples/js-hello-world --mode no-install\n```\n\n| Option | Description |\n|---------------|------------------------------------------------------------------------------------------|\n| `no-install` | `wasm-pack build` implicitly and create wasm binding without installing `wasm-bindgen`. |\n| `normal` | do all the stuffs of `no-install` with installed `wasm-bindgen`. |\n\n## Extra options\n\nThe `build` command can pass extra options straight to `cargo build` even if\nthey are not supported in wasm-pack. To use them simply add the extra arguments\nat the very end of your command, just as you would for `cargo build`. For\nexample, to build the previous example using cargo's offline feature:\n\n```\nwasm-pack build examples/js-hello-world --mode no-install -- --offline\n```\n\n
\n\n0 If you need to include additional assets in the pkg\ndirectory and your NPM package, we intend to have a solution for your use case\nsoon. [ā†©](#wasm-pack-build)\n" }, { "path": "docs/src/commands/index.md", "content": "# Commands\n\n`wasm-pack` has several commands to help you during the process of building\na Rust-generated WebAssembly project.\n\n- `new`: This command generates a new project for you using a template. [Learn more][new]\n- `build`: This command builds a `pkg` directory for you with compiled wasm and generated JS. [Learn more][build]\n- `pack` and `publish`: These commands will create a tarball, and optionally publish it to a registry, such as npm. [Learn more][pack-pub]\n\n### Deprecated Commands\n\n- `init`: This command has been deprecated in favor of `build`.\n\n[new]: ./new.html\n[build]: ./build.html\n[pack-pub]: ./pack-and-publish.html\n\n### Log levels\n\nBy default `wasm-pack` displays a lot of useful information.\n\nYou can cause it to display even *more* information by using `--verbose`, or you can silence *all* stdout by using `--quiet`.\n\nYou can also use `--log-level` to have fine-grained control over wasm-pack's log output:\n\n* `--log-level info` is the default, it causes all messages to be logged.\n* `--log-level warn` causes warnings and errors to be displayed, but not info.\n* `--log-level error` causes only errors to be displayed.\n\nThese flags are global flags, so they can be used with every command, and they must come *before* the command:\n\n```sh\nwasm-pack --log-level error build\nwasm-pack --quiet build\nwasm-pack --verbose build\n```\n" }, { "path": "docs/src/commands/init.md", "content": "# wasm-pack init (DEPRECATED)\n\nThis command has been deprecated in favor of `build`, which does the same thing, but is\na much more representative name for the command. [Read the docs for `build`.][build]\n\n[build]: ./build.html\n" }, { "path": "docs/src/commands/new.md", "content": "# wasm-pack new\n\nThe `wasm-pack new` command creates a new RustWasm project for you,\nusing [`cargo-generate`] under the hood.\n\nIt takes 3 parameters, name, template, and mode:\n\n```\nwasm-pack new --template