When checking out examples, the link to the GitHub source repo 404s

https://docs.wasmer.io/runtime/rust-integration/docs/runtime-rust-integration-examples-passing-data
https://github.com/wasmerio/docs.wasmer.io/tree/master/docs/runtime/rust-integration/examples/passing_data.rs

GitHub allows linking to specific commits instead of branches. This takes more work when updating the docs, but if related repositories are renamed or files moved, links still remain valid, since static documentation is linked against a fixed set of commits.

Moving the site

@syrusakbary and I agreed to get the docs out sooner rather than later, but we want to move all of the online Wasmer Resources under a single domain and repo on Gatsby 😄

Post MVP TODO

• Only show parts of the example?
• Add a way to include files from markdown to be able to show their source code.
• Add the Wasmer Logo to the header, and change header color? Actually, with the move, just re-use the same header component

It's important that our examples work so we should test them in CI.

Tasks

• Fix Rust CI - #45
• Implement C CI
• Implement JS CI

From: @syrusakbary

• Move the building from source for the Wasmer CLI into it’s own doc (outside of installation) https://docs.wasmer.io/runtime/cli/runtime-cli-installation
• In the Rust integration, the docs say “Next, let’s take a look at building a simple hello world!” (https://docs.wasmer.io/runtime/rust-integration/runtime-rust-integration-installation) but the next document is the reference API. Moving the reference API down should fix this
• The following pages: https://docs.wasmer.io/runtime/rust-integration/examples/hello-world/runtime-rust-integration-examples-hello-world, https://docs.wasmer.io/runtime/rust-integration/examples/passing-data/runtime-rust-integration-examples-passing-data, https://docs.wasmer.io/runtime/rust-integration/examples/host-functions/runtime-rust-integration-examples-host-function, https://docs.wasmer.io/runtime/rust-integration/examples/handling-errors/runtime-rust-integration-examples-handling-errors have the example links to the C-API example, not the rust one
• https://docs.wasmer.io/runtime/c-integration/runtime-c-integration-installation docs have wrong code text: rustup-init.exe
• C/C++ integration Reference API should go after Hello World (in the index)W
• Wasmer-JS should have a direct link to the js repo in the intro https://docs.wasmer.io/wasmer-js/wasmer-js
• WAPM intro should have a link to the wapm website https://docs.wasmer.io/wapm/wapm

We should have examples using WASI for all of our integrations

It seems that endtag instead of endtab in the Defining and importing the host function section (Ruby) breaks the tabs. Currently the "Ruby" tab is empty while there is a tab called "Untitled" with the content of the "Ruby" tab.

Fix: https://github.com/wasmerio/docs.wasmer.io/pull/127

Page: https://docs.wasmer.io/integrations/python/setup
Clicking on Examples link at the bottom, points to Javascript at https://docs.wasmer.io/integrations/js/wasi/browser/examples

Inspired by: https://twitter.com/jayadevanraja/status/1203272096823922688

Thank you! 😄 👍

The documentation with /integrations/go/setup.md shows a malformed go.mod file:

require (
    require github.com/wasmerio/wasmer-go v1.0.0
)

and should be written as:

require (
    github.com/wasmerio/wasmer-go v1.0.0
)

instead. The require block does not need to have the require keyword repeated on every line within the block as defined in the spec.

The same file also shows a not yet released version tag, but I suppose this will be corrected once v1.0.0 of the Go integration is released.

Mark and Nick Feedback

• Add links to relevant technologies (WebAssembly.sh, WAPM, WasiEnv, wasm-pack, etc...)
• Remove any lingering notion -> markdown errors?
• Implement Notion comments from ( @MarkMcCaskey and @nlewycky ) 😄
• Update image URLs inside markdown docs, from transferring from notion

Syrus Feedback

• Add the edit this page
• Double check that we link to the actual example directory in the examples, so people can view the end-to-end example project (#6 , @syrusakbary comment to double check on this)
• Searching feature Applied, will Take a few days before DocSearch gets back to us and we can integrate Moved to #11

Brandon Feedback

• Smaller brand font in top left (As in the word documentation is unbolded)
• Add icons or images to introduction
• Multiple sections to break up wall of text
• Home button may be removed (since left nav brand link to same)
• Provide links like (to introduction.html) this to each section (WasmerJS, etc): https://www.twilio.com/docs

Ivan Feedback

• Could we add links to previous and next section at the bottom of the pages? That is useful to avoid scrolling to the menu, opening it, scrolling and clicking on the next section.
• The header takes too much space though, can we shrink it? Moved to #12

Hi,

I was reading the example docs and trying to run the examples, however, they do not seem to be consistent.
For example, the hello world application (https://docs.wasmer.io/integrations/js/wasi/browser/examples/hello-world) is supposed to write Standard Output: Hello World!, however, when I run the example, I see Standard Output: hello world. Taking a look into the hello word source code (https://github.com/wasmerio/docs.wasmer.io/blob/e0f7639306bb4cf18cd0c23876b80f787d6b5876/integrations/shared/wat/wasi/helloworld.wat), it seems like the program only writes the hardcoded "hello world" string but ignores anything passed as an argument.
Also the transforming modules example does not output "Done", but it outputs nothing and the source code (https://github.com/wasmerio/docs.wasmer.io/blob/e0f7639306bb4cf18cd0c23876b80f787d6b5876/integrations/shared/wat/wasi/clocktimeget.wat) also does not include the string "Done".

Can you please make your examples consistent with the documentation.

Additionally, it would help to add in the documentation of the examples that the following needs to be added to the package.json file to make the examples work:

  "browserslist": [
    "last 1 Chrome versions"
  ]

This documentation starts with an example of host functions in Go.
https://docs.wasmer.io/integrations/examples/imports-and-exports

Then it refers to this documentation for the remainder of the example, but this documentation doesn't have an example in Go. Only in Rust.
https://docs.wasmer.io/integrations/examples/host-functions

This was reported on Spectrum. Our C and Rust passing-data examples don't do the same things:

The Rust one allocates memory on the heap and does not nul-terminate its string, the C one does everything on the stack and nul-terminates its string.

I think ideally the Wasm files should all do the same thing even if that's less idiomatic in the language. So Rust can use CStr, or C can memcpy into a null-terminated array when it wants to deal with strings.

I have the following defined in Go.

type exitCode struct {
	code int32
}

func (e *exitCode) Error() string {
	return fmt.Sprintf("exit code: %d", e.code)
}

func log(args []wasmer.Value) ([]wasmer.Value, error) {
	for _, a := range args {
		_, err := fmt.Println(a.Unwrap())
		if err != nil {
			return nil, &exitCode{1}
		}
	}

	return nil, nil
}

func registerHostFunctions(store *wasmer.Store, importObject *wasmer.ImportObject) {
	importObject.Register(
		"",
		map[string]wasmer.IntoExtern{
			"log": wasmer.NewFunction(
				store,
				wasmer.NewFunctionType(wasmer.NewValueTypes(), wasmer.NewValueTypes()),
				log,
			),
		},
	)
}

Now when I call this function from Rust in a guest function I get following failure in my Go binary.

$ go run .
failed to create module instance: Missing import: `./calculator_bg.js`.`__wbg_log_b500d075b2228a75`
Wasm exports:
func add(i32,i32) (i32,i32)
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x40ba64d]

goroutine 1 [running]:
main.main()
        /Users/marco/code/philips-internal/wasm-wasi/wasmer-go/main.go:106 +0x6ad
exit status 2

Without calling the log function from my Guest function all works flawlessly.

The code in Go that invokes the guest function looks like this. Error handling left out for the example here.

	engine := wasmer.NewEngine()
	store := wasmer.NewStore(engine)
	module, _ := loadWasm(store, "../calculator/pkg/calculator_bg.wasm")
	importObject := wasmer.NewImportObject()
	registerHostFunctions(store, importObject)
	instance, _ := wasmer.NewInstance(module, importObject)
        f, _ := instance.Exports.GetFunction("multiply")
        result, _ := f(3, 4)

The code in Rust looks as following and is build using wasm-pack.

use wasm_bindgen::prelude::*;

// When the `wee_alloc` feature is enabled, use `wee_alloc` as the global
// allocator.
#[cfg(feature = "wee_alloc")]
#[global_allocator]
static ALLOC: wee_alloc::WeeAlloc = wee_alloc::WeeAlloc::INIT;

#[wasm_bindgen]
extern "C" {
    fn log(s: &str);
}

#[wasm_bindgen]
pub fn add(a: i32, b: i32) -> i32 {
    log("Adding 2 numbers");
    // log(&format!("{}+{}", a, b));
    return a + b;
}

#[wasm_bindgen]
pub fn substract(a: i32, b: i32) -> i32 {
    log("Substracting 2 numbers");
    // log(&*format!("{}-{}", a, b));
    return a - b;
}

#[wasm_bindgen]
pub fn multiply(a: i32, b: i32) -> i32 {
    log("Multiplying 2 numbers");
    // log(&*format!("{}x{}", a, b));
    return a * b;
}

#[wasm_bindgen]
pub fn divide(a: i32, b: i32) -> f32 {
    log("Dividing 2 numbers");
    // log(&*format!("{}/{}", a, b));
    return a as f32 / b as f32;
}

Links for slack and spectrum chat are broken. As pointed out by a community member Derrick Hammer

mac pro M1 follow https://docs.wasmer.io/integrations/js/wasi/server/examples/hello-world

npm install had been installed.

 npm install  @wasmer/wasi 
 node index.js                                    
node:internal/modules/cjs/loader:942
  throw err;
  ^

Error: Cannot find module '@wasmer/wasi/lib/bindings/node'
Require stack:
- /Users/williamlee/wasm/wasmer-js-node-hello-world/index.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:939:15)
    at Module._load (node:internal/modules/cjs/loader:780:27)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/Users/williamlee/wasm/wasmer-js-node-hello-world/index.js:3:20)
    at Module._compile (node:internal/modules/cjs/loader:1105:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Module._load (node:internal/modules/cjs/loader:827:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/Users/williamlee/wasm/wasmer-js-node-hello-world/index.js' ]
}

Node.js v18.0.0

Applied with [email protected], will Take a few days before DocSearch gets back to us and we can integrate.

Rust CI was broken in 5c49b94, we're no longer testing most of the Rust integrations.

I'm also personally not a fan of the duplication of the new layout as it makes testing and updating slower and more difficult.

On this page:

https://wasmerio.github.io/wasmer/c/runtime-c-api/

is a link to

https://docs.wasmer.io/integrations/c/examples

in the examples section. It doesn't work.

Page: https://docs.wasmer.io/integrations/c

Page not found when clicking 'Wasmer C API' subpage, which points to https://docs.rs/wasmer-c-api/*/wasmer_c_api/wasm_c_api/index.html

"The header takes too much space though, can we shrink it?"

The wasmer-js documentation needs some Mac-specific details added to it

Parcel depends on node-gyp which (on a Mac at least) depends on the Xcode command line tools, which in turn, depend on Xcode being installed

Happy to add these details myself...

Currently, this just prints out the string "Done!". Which was perfect for when we were testing / building the wasm-trasnformer, but now it does not make much sense for the docs 😄

relates to wasmerio/docs.wasmer.io#20 (comment)

First, before I claim there's a bug, are there any undocumented prerequisites needed to get this example working? For instance, should duktape work without first needing to wapm install it?

When running the coding shown here, I get a pop-up prompt as expected and if I enter a numeric value, the prompt reappears. If I then cancel the prompt, the expected value is displayed in both the DOM and the console.

Odd behaviour, but OK...

If I enter any non-numeric value however, the following stack trace appears in the console without any values displayed in either the DOM or the console

index.js:119 RuntimeError: unreachable
    at abort (wasm-function[1250]:0xe7264)
    at duk_err_longjmp (wasm-function[440]:0x3629e)
    at duk_err_create_and_throw (wasm-function[23]:0x159a)
    at duk_err_handle_error_fmt (wasm-function[205]:0x1623d)
    at duk__getvar_helper (wasm-function[700]:0x63b40)
    at duk_js_getvar_activation (wasm-function[1173]:0xdbdc2)
    at duk__js_execute_bytecode_inner (wasm-function[1160]:0xd762b)
    at duk_js_execute_bytecode (wasm-function[1146]:0x9dbcb)
    at duk__handle_call_raw (wasm-function[38]:0x2a5d)
    at duk_handle_call_unprotected (wasm-function[33]:0x1d2e)

The Demo in : https://docs.wasmer.io/integrations/js/reference-api/wasmer-wasi

const browserBindings = require("@wasmer/wasi/lib/bindings/browser");
// for Node:
// const nodeBindings = require("@wasmer/wasi/lib/bindings/node");

// omit other part

That has am error: Cannot resolve dependency '@wasmer/wasi/lib/bindings/browser

After look inside, @wasmer/wasi "@wasmer/wasi": "^0.10.0" has directory lib in npm module, but the latest version does't.

So, the question is, is there the way run wasi in browser?

Sorry I'm a brand new beginner to WASM so maybe I'm missing something, but the ... main first example of Wasmer seems to be incomplete?

It jumps from "creating an instance" to "running the example" and doesn't seem to actually show the code for invoking add_one?

The code seems to be there, as I'd expect, it's just not documented: https://github.com/wasmerio/wasmer/blob/master/examples/instance.rs

Upon reconsideration, it looks like maybe this is intentional:

I'm not sure this is a good idea. I get the intent to split out "instantiate", "call guest func", etc, but it's very odd that the very first example walks through basically every step except the actual core function call. Enough that I stopped to go look for the source code to see if I was missing something. This confusion was further backed up by the "call guest function" example not returning to the simple instance example to demonstrate the call, but instead introducing an entire new example.

Obviously this is subjective, so feel free to disregard/close/whatever, but hopefully the outside newbie perspective was worth sharing! Cheers, looking forward to learning more, thanks for your work on this.

I was facing the following issues when using the hello-world example:

• The index.html is not loading correctly in chrome, because type="module" is not specified in the <script> tag.
• When instantiating the WASI object no preopens are specified. This is working fine for the hello-world example, but when trying to do any additional File IO errors will occur. I am not sure if I overlooked some obvious documentation for this parameter, but it would've helped me a lot if something like preopens: { '/': '/' } could be included in the example.
• When running npm run dev the helloworld.wasm cannot be loaded, because it is not copied from the static directory to the dist directory and parcel does not serve it from the static directory
• It would be great to have a working npm run build target to be able to host the static files.

The latest nomenclature prefers using Wasm instead of uppercase WASM.

We should change all our nomenclature back to Wasm cc @ChrisWhealy

relates to #21

This can cause some issues for first time users as found in the PR 😄

I found some issues in the passing data example:
https://docs.wasmer.io/integrations/c/examples/passing-data

First, the path to the wasm module (example-wasienv-wasm/strings-wasm-is-cool/strings-wasm-is-cool.wasm) seems to a different one than the one pointed to use.

On the premise that the correct one is this: https://github.com/wasmerio/docs.wasmer.io/blob/master/integrations/shared/c/passing-data.c, there are some fixes to be made.

First, when calling the add_wasm_is_cool function, the length of the original string should be passed as an argument. The second one is that the function that returns the pointer to the byte_buffer is called get_wasm_memory_buffer_pointer instead of get_buffer_pointer

Hi,
I got this error when compiling passing-data.c example:

passing-data.c: In function ‘get_length_of_memory’: passing-data.c:132:36: warning: passing argument 1 of ‘wasmer_memory_data_length’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] 132 | return wasmer_memory_data_length(memory); | ^~~~~~ In file included from passing-data.c:2: /home/osboxes/wasmer-c-api/include/wasmer.h:1174:53: note: expected ‘wasmer_memory_t *’ {aka ‘struct <anonymous> *’} but argument is of type ‘const wasmer_memory_t *’ {aka ‘const struct <anonymous> *’} 1174 | uint32_t wasmer_memory_data_length(wasmer_memory_t *memory);

Could anyone please help? I am using this api:
https://github.com/wasmerio/wasmer/releases/download/0.16.2/wasmer-c-api-linux-amd64.tar.gz

Thanks.