Method for initialization?

[halzy]

When looking through the project and examples, the Router is often used in the main function that is annotated with #[fetch]. This causes the router to be created for each request. Have you considered a way to split this so that there is an initialization phase?

[nilslice]

Yes, that has come up and would like to have a solution. If you've got suggestions, please share! Ideally we can find a way to prevent the router from forcing all of its data () types to be wasm_bindgen'd by the end-user... but I'm not sure how to go about this. In order to share the router between requests, I'd assume it needs to be assigned to something on the JS globalThis?

[halzy]

Hrm, perhaps users could use std::sync::Once for the same effect. Another option would be to make the routes static, a macro could probably do that.