Describe the Bug

The yarn equivalent for npm init wasm-app www is `yarn create wasm-app www', but it doesn't work with this module.

Steps to Reproduce

1. mkdir blah
2. cd blah
3. yarn create wasm-app www
4. See error

Expected Behavior

The www directory gets created like when I run npm init wasm-app www.

Actual Behavior

Here's my output:

wt@XXXXXXX:~/projects/blah$ yarn create wasm-app www
yarn create v1.22.4
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Installed "[email protected]" with binaries:
      - create-wasm-app
/bin/sh: 1: /home/wt/.yarn/bin/create-wasm-app: not found
error Command failed.
Exit code: 127
Command: /home/wt/.yarn/bin/create-wasm-app
Arguments: www
Directory: /home/wt/projects/blah
Output:

info Visit https://yarnpkg.com/en/docs/cli/create for documentation about this command.

Additional Context

I was following the project tutorial except that I wanted to use yarn.

Summary

Going through the rustwasm book's Hello world, I was unable to generate the www directory with the suggested command:

npm init wasm-app www

This command generates a package.json file but not the www directory, as in rustwasm/book#174 .

Upgrading to Node 12 seemed to solve the issue. My question is if this behavior is expected for the node version I was using (v8.10.0) and, if so, what is the minimum version that produces the desired directory as in the the rustwasm book?

Additional Details

OS: Ubuntu 18.04.4.

I'm trying your example integrate into my application written with using express framework but get error in browser(Firefox v.60)
"Loading failed for module with source “http://localhost:3000/public/javascripts/bootstrap.js”
html:
"

In Folder public/javascript next files unchanged as an example:
bootstrap.js
HelloWasm_bg.wasm
HelloWasm.d.ts
HelloWasm.js
index.js

WebAssembly is cool!!!Help me!

Motivation

The utility assumes git is already installed and fails miserably if that is not the case (throws an error).

Proposed Solution

IMO, it is good to validate the respective case upfront and warn appropriately.

Alternatives

N/A

Additional Context

N/A

I mean it dependencies have updated A lot and there are many breaking changes

webpack              ^4.29.3  →  ^5.74.0
webpack-cli           ^3.1.0  →  ^4.10.0
webpack-dev-server    ^3.1.5  →  ^4.11.1

I guess you shouldn't have used webpack then 😝
simply use --target web I suppose.

Rust newbie here,
Just following the tutorial and I've reached midway through section 4.4 where I've run into a weird issue. I try building the project and running npm run start, that's when I got the error message:
ERROR in ./index.js 1:20
Module parse failed: Unexpected token (1:20)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

import { Universe } as wasm from "wasm-game-of-life";
| const pre = document.getElementById("game-of-life-canvas");
| const universe = Universe.new();
@ ./bootstrap.js 4:0-20

How would I fix this issue?

I'm trying to build a custom language code ditor with linting, syntax check etc.,

My opinon is to use rustwasm/web_sys crate to build and manage dom from rust. But on the initial few run Native JS dom binding seems to be performing better than rustwasm.

Do you have any performance metics comparing web_sys and native js?

Current version of webpack-dev-server is 3.1.5, which will trigger npm's audit. Update to version 3.1.6 or later to mute this audit.

I just tried to create an instance of create-wasm-app by executing npm init wasm-app.
I was expecting the project initialization to succeed.
Instead, I got this error log:

~/Development/accept  npm init wasm-app
npx: installed 1 in 2.048s
cloning the template failed!

Describe the Bug

npm init wasm-app www fails.

Versions

>node --version
v20.16.0
>npm --version
10.8.2

Error

>npm init wasm-app www
npm error could not determine executable to run
npm error A complete log of this run can be found in: C:\Users\User\AppData\Local\npm-cache\_logs\2024-07-25T11_30_21_907Z-debug-0.log

// 2024-07-25T11_30_21_907Z-debug-0.log
0 verbose cli C:\Program Files\nodejs\node.exe C:\Users\User\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js
1 info using [email protected]
2 info using [email protected]
3 silly config load:file:C:\Users\User\AppData\Roaming\npm\node_modules\npm\npmrc
4 silly config load:file:C:\Users\User\Documents\_G\Source code\ATBA\wasm_example_2\.npmrc
5 silly config load:file:C:\Users\User\.npmrc
6 silly config load:file:C:\Users\User\AppData\Roaming\npm\etc\npmrc
7 verbose title npm init wasm-app www
8 verbose argv "init" "wasm-app" "www"
9 verbose logfile logs-max:10 dir:C:\Users\User\AppData\Local\npm-cache\_logs\2024-07-25T11_15_43_784Z-
10 verbose logfile C:\Users\User\AppData\Local\npm-cache\_logs\2024-07-25T11_15_43_784Z-debug-0.log
11 silly logfile start cleaning logs, removing 1 files
12 silly logfile done cleaning log files
13 silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368
14 verbose shrinkwrap failed to load node_modules/.package-lock.json missing from node_modules: ../../../../../../../../usr/local/lib/node_modules/create-wasm-app
15 http fetch GET 200 https://registry.npmjs.org/create-wasm-app 311ms (cache revalidated)
16 verbose stack Error: could not determine executable to run
16 verbose stack     at getBinFromManifest (C:\Users\User\AppData\Roaming\npm\node_modules\npm\node_modules\libnpmexec\lib\get-bin-from-manifest.js:17:23)
16 verbose stack     at exec (C:\Users\User\AppData\Roaming\npm\node_modules\npm\node_modules\libnpmexec\lib\index.js:202:15)
16 verbose stack     at async Init.execCreate (C:\Users\User\AppData\Roaming\npm\node_modules\npm\lib\commands\init.js:136:5)
16 verbose stack     at async Init.exec (C:\Users\User\AppData\Roaming\npm\node_modules\npm\lib\commands\init.js:44:14)
16 verbose stack     at async Npm.exec (C:\Users\User\AppData\Roaming\npm\node_modules\npm\lib\npm.js:207:9)
16 verbose stack     at async module.exports (C:\Users\User\AppData\Roaming\npm\node_modules\npm\lib\cli\entry.js:74:5)
17 verbose pkgid [email protected]
18 error could not determine executable to run
19 verbose cwd C:\Users\User\Documents\_G\Source code\ATBA\wasm_example_2
20 verbose os Windows_NT 10.0.22631
21 verbose node v20.16.0
22 verbose npm  v10.8.2
23 verbose exit 1
24 verbose code 1
25 error A complete log of this run can be found in: C:\Users\User\AppData\Local\npm-cache\_logs\2024-07-25T11_15_43_784Z-debug-0.log

Steps to Reproduce

This tutorial.

Expected Behavior

npm init wasm-app www creates www folder.

Actual Behavior

npm init wasm-app www fails.

this is intended for use with the wasm-pack tutorial, which has you write a library which then u are expected to import in the app this creates. hard to test this without actually including a library, but that is supposed to be the exercise left to the user. i think i'll publish without it for now, but we should consider whether adding an example, e.g. https://www.npmjs.com/package/@ag_dubs/hello-wasm

If the optional folder is more than one level deep, mkdirSync will fail. I know this is true for some node versions at least, but I have not checked the latest if the API changed (I doubt it).
One solution is use package mkdirp, another is manually splitting path string and creating a folder for each.

This is for consuming libraries made with wasm-pack and wasm-pack-template.

If people want one full package for creating webpages, point them to rust-webpack-template.

Summary

The tutorial at https://rustwasm.github.io/docs/book/game-of-life/implementing.html constantly mentions to just wasm-pack build and refresh the webpage, but does not say anything about restarting the npm run start command after each build. Just building doesn't seem to trigger a node recompile to get the updated library into the webpage. I have to restart the node server to get it to load the new version. How can I enable the server to monitor the wasm lib too, or even the .rs files, and automatically rebuild if it detects a change?

I am following along this tutorial: https://rustwasm.github.io/book/game-of-life/hello-world.html

At the "Putting it into a Webpage" step the following command fails:

$ npm init wasm-app
command not found: create-wasm-app

CI should

• run the local version of the template (not 100% sure how to do this with npm init and local packages)
• verify that it builds afterwards (npm install && ./node_modules/.bin/webpack)

am I missing anything else it should do?

Describe the Bug

I have followed the example https://rustwasm.github.io/docs/book/game-of-life/implementing.htm and modified it to use the petgraph crate and try to build a module to use wasm to store tree structure for JS.

The module compiles and seems to work following the tutorial, however if I tried to include the package locally in another project e.g. https://github.com/bbofrk/trying-wasm, or even tried publishing the package on npm (https://www.npmjs.com/package/wasm-tree-structure) then installing in into another project. I am getting the same error

WebAssembly module is included in initial chunk. friendly-errors 09:45:56
This is not allowed, because WebAssembly download and compilation must happen asynchronous.

Steps to Reproduce

1. clone https://github.com/bbofrk/trying-wasm
2. run npm install
3. run npm run dev
4. See error

Expected Behavior

Should not see compile error

Actual Behavior

WebAssembly module is included in initial chunk. friendly-errors 09:45:56
This is not allowed, because WebAssembly download and compilation must happen asynchronous.

Additional Context

This might have something to do with my webpack.config.js or in this case nust.config.js but I could not tell what should be included. So apologis in advance if its my personal error

• Prompt for the user's preferred bundler
• Initialize the template with that bundler pre-configured

Maybe using yeoman?

cc @ashleygwilliams @sendilkumarn

I have a bundle like this that is not electron-ready apparently:

const path = require('path').join(__dirname, 'my_project_bg.wasm');
const bytes = require('fs').readFileSync(path);
let imports = {};
imports['./my_project'] = require('./my_project');

const wasmModule = new WebAssembly.Module(bytes);
const wasmInstance = new WebAssembly.Instance(wasmModule, imports);
module.exports = wasmInstance.exports;

Trying to run it in Electron I get this error:

WebAssembly.Compile is disallowed on the main thread, if the buffer size is larger than 4KB. Use WebAssembly.compile, or compile on a worker thread.

Do someone used an app created with create-wasm-app in electron?