Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/panoptix-za/web-bundler

Bundles a Rust WebAssembly frontend application for publishing
https://github.com/panoptix-za/web-bundler

build-script cargo frontend rust seed wasm wasm-pack web

Last synced: about 2 months ago
JSON representation

Bundles a Rust WebAssembly frontend application for publishing

Awesome Lists containing this project

README

        

Web Bundler
===========

[![crates.io](https://img.shields.io/crates/v/web-bundler.svg)](https://crates.io/crates/web-bundler)
[![status-badge](https://ci.codeberg.org/api/badges/worthe-it/web-bundler/status.svg)](https://ci.codeberg.org/worthe-it/web-bundler)

Manages the building of WebAssembly single page app frontends from a
build.rs script so that they can easily be embedded into Rust API
projects.

Internally, the bundler uses
[wasm-pack](https://github.com/rustwasm/wasm-pack) to do the actual
webassembly compilation.

## Prerequisites

From a clean Rustup-based Rust installation, there are no additional
steps. Web Bundler will download and install any dependencies it
needs.

For Rust installations that are not done with Rustup, you will need to
add the `wasm32-unknown-unknown` compilation target manually (see the
[wasm-pack docs](https://rustwasm.github.io/docs/wasm-pack/prerequisites/non-rustup-setups.html)
for details on how to do this).

## Running the Demo Example

There is an example usage in the [example directory](./example). To
run the example, open a terminal in the example directory and run
`cargo run`. Then, open a web browser and navigate to
. You should see a Seed web application.

## Usage

Web-bundler expects you to have two projects: a frontend project using
a single page app framework (like [Seed]), and a backend project using a
web server framework (like [warp]).
These projects should be in a common
workspace.

### Changes to your frontend project

1. Update your index.html to allow templating in Javascript and CSS.

Specifically, you need to add `{{ stylesheet | safe }}` to the
`` section, and `{{ javascript | safe }}` to the end of the
``. Optionally, if you want to set the base url, add `` to the `` as well.

See the example [frontend index.html](./example/frontend/index.html).

2. Create a root stylesheet for your app called `./css/style.scss`.

This stylesheet will be compiled to CSS, and embedded directly into
your index.html file.

See the example [frontend style.scss](./example/frontend/css/style.scss).

3. Put all of your static assets in the `static` directory

All files in the static directory will be copied directly to a static
folder in the output directory.

See the example [frontend static directory](./example/frontend/static/).

### Changes to your API project

1. Update your Cargo.toml to depend on your frontend project and web-bundler

We depend on the frontend project in Cargo.toml so that Cargo knows to
rerun build.rs whenever the frontend project changes.

See the example [backend Cargo.toml](./example/backend/Cargo.toml).

2. Add a build.rs script that calls web-bundler for your frontend

See the example [backend build.rs](./example/backend/build.rs).

3. Use [Rust Embed](https://lib.rs/crates/rust-embed) to embed your built frontend into your API binary

See the example [backend main.rs](./example/backend/main.rs). Our
example uses the [warp web server][warp]. Rust Embed also has examples for
other web servers in [their repo](https://github.com/pyros2097/rust-embed/tree/master/examples).

## target and web-target directories

When web-bundler compiles the frontend, it overrides the default
target directory to be `web-target` instead of `target`. This is done
because, if the backend and frontend are in the same workspace, Cargo
will already be locking `target` while running the build.rs
script.

[warp]: https://github.com/seanmonstar/warp
[Seed]: https://github.com/seed-rs/seed

#### License


Licensed under either of
Apache License, Version 2.0
or
MIT license
at your option.



Unless you explicitly state otherwise, any contribution intentionally submitted
for inclusion in this crate by you, as defined in the Apache-2.0 license, shall
be dual licensed as above, without any additional terms or conditions.