-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: update README #30 #31
Open
scriptjs
wants to merge
1
commit into
wasm-tool:master
Choose a base branch
from
scriptjs:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,10 +8,34 @@ | |
yarn add --dev @wasm-tool/wasm-pack-plugin | ||
``` | ||
|
||
### Rust lang | ||
|
||
Rust >= `rustc 1.31.0-nightly` is required to fetch and compile rust wasm. Rust is installed and managed using [`rustup`](https://rustup.rs/) | ||
|
||
### `wasm-pack` | ||
|
||
We expect `wasm-pack` to be in your `$PATH`. See [installation here](https://github.com/rustwasm/wasm-pack/blob/master/docs/src/setup.md#installing-wasm-pack). | ||
|
||
### `wasm-bindgen-cli` | ||
|
||
`wasm-bindgen` is a build requirement for `wasm-pack` and a dependency of `wasm-bindgen-cli`. To verify installation, run: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. But wont |
||
|
||
``` | ||
which wasm-bindgen | ||
``` | ||
|
||
If a path is not returned, install `wasm-bindgen-cli` using the cargo package manager: | ||
|
||
``` | ||
cargo +nightly install wasm-bindgen-cli | ||
``` | ||
|
||
Following installation, you may be prompted to upgrade the `wasm-bindgen` dependency. This can be done using the following: | ||
|
||
``` | ||
cargo update -p wasm-bindgen | ||
``` | ||
|
||
## Usage | ||
|
||
Add the loader in your `webpack.config.js`: | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fitzgen mentioned that this isn't needed. Could you please take a look @fitzgen
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using the >= 0.5.0 versions of wasm-pack will automatically install the wasm-bindgen CLI for you (and the right version!) if necessary, so it shouldn't be a prerequisite to already have it installed anymore.
Just sent #36 too since we generally don't want to encourage
-m no-install
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure what you mean, I ran into issue #30 with 0.5.1 of wasm-pack.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That was because
no-install
mode was used, which forces wasm-pack into not downloading the w32-u-u targetThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There have been commits since then that removed the use of no-install, btw.