Game-of-Life | A Game of Life implementation in JavaScript

This might be not the most helpful answer, but the answer is you currently can't - there is an open issue on wasm-bindgen repo tracking future support for debugging but it's not yet supported: https://github.com/rustwasm/wasm-bindgen/issues/2389

Note that even when it will be, you'll need to use browser DevTools not CodeLLDB for WebAssembly debugging, since you need a JavaScript-capable environment.

When match gives Ok(Config::WorldDef { ... dead_char: Some(&d), alive_char: Some(&a), } the two last references are slices from Strings owned by args_vec (accessed via args_slice).

When the function exits, args_vec does not exist any more, thus the references in the result would be dangling if Rust didn't complain.

I suggest that you store Strings instead of &str in the dead_char and alive_char member; this way, the result could take ownership of these to strings from args_vec. By the way, if you do that, I'm not certain args_slice is useful; I think you can just consume args_vec in the match statement because it won't be used afterwards.

In the definition of new-timer, you're trying to get the grd field of cv.

And although cv is an instance of the class new-canvas%, its type does not include that field. You need to create a new Class type for new-canvas%. By convention, it should be a capitalized version like New-Canvas%.

I had a similar error when I updated the version of copy-webpack-plugin from the one specified in the tutorial files due to a security alert. The format of the config parameters changed at the same time, so I had to change them to match.

The tutorial had "copy-webpack-plugin": "^5.0.3" and I upgraded to "copy-webpack-plugin": "^6.0.3", and in webpack.config.js I had to change

It turns out that this is not expected behavior; instead it is a bug with wasm-pack.

The issue can be resolved for now by adding the following to the project's cargo.toml:

Your problem is how you update the cells. The rules are:

• a live cell dies if it doesn't have 2 or 3 live neighboure;
• a dead cell comes alive if it has 3 live neighbours.

That means that you must consider the current state of the cell to determine its next state, but your code doesn't do that. (It also means that it is enough to count the live neighbours.)

With the rules above, your update code should look like this:

The www and pkg folders contain the source files you need, but you do not have a static site yet. The create-wasm-app template uses Webpack, so you need to build the final output by running npm run build in the www folder. This will create a subfolder named dist which contains the actual static files that can be placed on your web server.

You are probably facing with a submodule.
Your www folder is pointing to another git repository.

Please check in Github, if beside the folder name you have an hash, something like: www @ a773f5e.

If this is correct, you should have also a file named .gitmodules in the root of the project.

You can initialize and clone the submobule repository with the command: git submodule update --init

Edit

This is a gitlink.

Typing git ls-tree HEAD www you should see the special mode 160000 at the very left. It is recorded from git as a submodule, but it isn't.

To recover you need to:

1. remove from the index the gitlink: git rm --cached www
   This command won't delete your files or your changes from the disk, just from the git's working index.
2. delete the .git folder: rm -fr www/.git
3. add the www folder to the index: git add www
4. commit and push

Now your www folder should act as a normal folder.

As listed in the Cargo documentation, you can create a .cargo/config and specify the target: