An investigation into an enterprise without JavaScript
Blazor is on its way up, as are several Go WebAssembly frameworks and of course there are plenty of Rust Frameworks under development.
Personally I'm not comfortable using frameworks unless I understand how they work, so this project will likely end up becoming my own simple web framework. There will be likely be no backend but how to do this is a primary consideration.
In parallel I'm doing investigations into more "gamey" software with rustwasm, but I need to keep these separate to reduce confusion.
Also interested in related topics:
- wasi - could this replace docker?
- gRPC in Rust - could this be an E2E secure microservices website built entirely in Rust?
- Rust WASM book - The official resource on Rust + Web Assembly
- Wasm-pack book - the current/future of build of rust/wasm applications, uses npm for now
- Wasm Bindgen - wasm-bindgen reference inc WebGL examples & CI/CD
- Wasm Bindgen examples
- GitHub Actions context properties
- GitHub Actions Node example
- GitHub Actions Blazor example
wasm-pack build --target web build wasm package without a bundler
wasm-pack test --headless --firefox run tests in headless browser
wasm-pack publish publish to npm, doubt I'll be doing this.
cargo install https - install the https crate into the default directory $HOME/.cargo/bin
http - launch http server locally
- Rust program
- wasm-bindgen for communicating between WebAssembly and JavaScript.
- console_error_panic_hook for logging panic messages to the developer console.
- wee_alloc, an allocator optimized for small code size.
- Testing
- GitHub Actions
- Development server
- Https - run local web server with no non-rust dependencies