Thiago Santos

I followed your steps and I had no errors. I implemented both no `.ext` and `.ext` versions. I think you have a broken gradle version or you IDE needs clear...

Hey guys, the voyager owner is very busy and his wife is pregnant. Updates will come soon. Stay up to date.

@luludevmuniz try `./gradlew -Pversion=1.0.0 publishToMavenLocal`

There is a little sample using WASM [here](https://github.com/adrielcafe/voyager/blob/main/samples/multiplatform/src/jsMain/kotlin/main.js.kt). But the repo is not updated with latest Kotlin WASM release.

Sorry guys. I can't. You will have to wait for owners review to check and avoid breaking changes.

@osrl Checkout pull request #217

Without a routing system this will not be easy to be handled on Voyager. Browser stack is to limitaded to store all voyager stack info and all browser history info...

Sharing my workaround to this. It is not the better approach but works: Tree: ``` - root-project - build-logic - domain-model - platforms - ... - gradle.properties - settings.gradle.kts ```...

The `Voyager` integration module has no support to web history and the version in `javascript` module is experimental. My knowledge in browser history is too limited. I made based on...

Nice. I updated the `javascript` integration to support history modes. Hash `/#/`, Html5 History and Memory. Most of these behaviors I will export to `voyager` integration too.