Fullstack example auth is panicking #2942
Labels
Comments
|
Can you please double check your version? You mentioned you are using dioxu 0.5 but your error says otherwise. That file structure is with the latest dioxus(0.6). Also the below error COULD be from the mistached 0.5 client and 0.6 dioxus. |
|
Are you running examples directly from the git repo? If so you most likely need the latest |
matthunz
added
fullstack
|
I believe there should be a clear instruction on how to run the examples, especially for the crates under https://github.com/DioxusLabs/dioxus/tree/main/examples I tried to run the fullstack-auth example and it never worked for me ❯ pwd
/home/chung/repos/dioxus/examples/fullstack-auth
❯ dx -V
dioxus 0.6.0-alpha.2 (9816b40)
❯ dx serve --platform fullstackVisiting http://127.0.0.1:8080 EDITOf course this is my 5th time forgotting about the port is on 3000 rather than 800 |
|
I also get this same error with running a full-stack using dx new and then upgrading dioxus version of the project. The Dioxus.toml file The Cargo.toml file: I am using a custom port because I get error with running more than one socket or something otherwise. opening the browser gives the following:
|
|
The main.rs is the same as in the template. The only thing I changed is add the bulma css file and link them into the dioxus.toml. I see that method is obsolete, but I should have still been able to run the software for the first time I would have thought. Verbose output of dx server: |
If you are using a custom port, the CLI doesn't know about that port. You need to either open the port your server is running on (default 8080) in your browser manually or use the port the dioxus cli gives in your fullstack application |
|
Yes the above results were all with using --port argument on the cli. You will notice the cli is using this custom port in its output that I have pasted above. |
The port the CLI is using shouldn't matter as long as it doesn't conflict with your backend. Are you using the port
|
|
I got the fullstack example Then I tried to extract the exampe into its own repository. Everything worked fine with one minor glitch: I started getting these network requests every 5 seconds from the client: My 'newbie' theory is that I get these since I could not figure out how to specify the "web/hydrate" feature when coding from outside the dioxus repo. This is the Cargo.toml in my extracted repo, any suggestions? |
Those requests are the hot reloading system trying to connect. Make sure you build in release mode with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
I tried to run the fullstack auth example. But it return errors:
Steps To Reproduce
Steps to reproduce the behavior:
Expected behavior
No Error and I can see on the browser
Environment:
Questionnaire
The text was updated successfully, but these errors were encountered: