Skip to content

jcbhmr/setup-wasm-tools

Use this GitHub action with your project
Add this Action to an existing workflow or create a new one
View on Marketplace

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

31 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Setup wasm-tools

πŸ‘©β€πŸ’» wasm-tools installer for GitHub Actions

- uses: jcbhmr/setup-wasm-tools@v2 - run: cargo build --target wasm32-wasi - run: wasm-tools print target/wasm32-wasi/debug/*.wasm

πŸŸͺ Installs wasm-tools globally
πŸ”’ Supports semver ranges
πŸ“ Caches the wasm-tools installation

Usage

GitHub Actions GitHub

πŸš€ Here's what you're after:

on: push jobs: job: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: jcbhmr/setup-wasm-tools@v2 - run: cargo build --target wasm32-wasi - run: wasm-tools print target/wasm32-wasi/debug/*.wasm

Inputs

  • wasm-tools-version: Which version of wasm-tools to install. This can be an exact version specifier such as 1.0.0 or a semver range like ~1.0.0 or 1.x. Use latest to always install the latest release. Defaults to latest.

  • wasm-tools-token: The GitHub token to use when fetching the version list from bytecodealliance/wasm-tools. You shouldn't have to touch this. The default is the github.token if you're on github.com or unauthenticated (rate limited) if you're not on github.com.

Outputs

  • wasm-tools-version: The version of wasm-tools that was installed. This will be something like 1.0.0 or similar.

  • cache-hit: Whether or not wasm-tools was restored from the runner's cache or download anew.

Development

Node.js

How do I test my changes?
Open a Draft Pull Request and some magic GitHub Actions will run to test the action.

About

πŸ‘©β€πŸ’» wasm-tools installer for GitHub Actions

Topics

Resources

Stars

Watchers

Forks

Packages

No packages published

Contributors 3

  •  
  •  
  •