Support static assests in handlers about wasm-workers-server HOT 4 CLOSED

This is a relevant feature for moderm websites. This will allow to build and publish complete websites without having to inject CSS, HTML or JS static code into the wasm compiled binary.

In the end, we will implement this by using a third approach: create a static folder to add static file inside. In this way, we don't need to add any extra configuration as it will work out of the box.

The static prefix won't be added to the files. Based on this structure:

.
├── docs
│   ├── index.js
│   └── static
│       └── intro.jpg
├── index.js
└── static
    └── robots.txt

Wasm Workers Server will init the following routes:

Handlers:
  - /
  - /docs

Static assets:
  - /robots.txt
  - /docs/intro.jpg

This convert static into a reserved word, so you cannot create static folders to host handlers. A static/index.js file will be managed as "static" file and not as a handler.

from wasm-workers-server.

After revisiting it, we plan to allow only a root static folder for the initial version. Every application is recommended to run on its own wws process. Having multiple static folders inside a project doesn't provide many advantages as they can be also coded as a subfolder in the initial folder:

.
├── docs
│   └── index.js
├── index.js
└── static
    └── docs
       └── intro.jpg
    └── robots.txt

Will be the same as:

.
├── docs
│   ├── index.js
│   └── static
│       └── intro.jpg
├── index.js
└── static
    └── robots.txt

To keep the usage simple, we will focus on the single static folder approach.

from wasm-workers-server.

Instead of static, we will use public as it's a common convention in web frameworks like NextJS, Astro, Remix, Ruby on Rails.

from wasm-workers-server.

As part of this feature, we should also support static .html files. In this way, we can create static sites and add dynamic features using wasm modules.

from wasm-workers-server.