fix: remove unexported import test from high level data types example

torch2424 · Jan 27, 2023 · b6d1252 · b6d1252
1 parent fce82ed
commit b6d1252
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 8 deletions.
diff --git a/...with-wasm-bindgen/passing-high-level-data-types-with-wasm-bindgen.rust.en-us.md b/...with-wasm-bindgen/passing-high-level-data-types-with-wasm-bindgen.rust.en-us.md
@@ -36,10 +36,7 @@ Next, lets create an `index.js` file to load and run our wasm output. Now that w
 // Outputted wasm-bindgen ES Module. As well as importing
 // the named exports that are individual wrapper functions
 // to facilitate handle data passing between JS and Wasm.
-import wasmInit, {
-  add_wasm_by_example_to_string,
-  test
-} from "./pkg/strings.js";
+import wasmInit, { add_wasm_by_example_to_string } from "./pkg/strings.js";
 
 const runWasm = async () => {
   // Instantiate our wasm module

diff --git a/...with-wasm-bindgen/passing-high-level-data-types-with-wasm-bindgen.rust.pt-br.md b/...with-wasm-bindgen/passing-high-level-data-types-with-wasm-bindgen.rust.pt-br.md
@@ -36,10 +36,7 @@ A seguir, criamos um arquivo `index.js` para carregar e rodar o nosso módulo wa
 // Outputted wasm-bindgen ES Module. As well as importing
 // the named exports that are individual wrapper functions
 // to facilitate handle data passing between JS and Wasm.
-import wasmInit, {
-  add_wasm_by_example_to_string,
-  test
-} from "./pkg/strings.js";
+import wasmInit, { add_wasm_by_example_to_string } from "./pkg/strings.js";
 
 const runWasm = async () => {
   // Instantiate our wasm module