Rust Perseus __ Debugging 하는 법(FullStack)

Engine-side logging
However, if you try to, say, call dbg!() in your build-time logic, you might discover that you get absolutely zilch output in the console unless the whole process fails. This is because Perseus takes the conservative route, and only prints the output of its undelrying calls to cargo if the build process fails. This can make subtle logic errors very difficult to debug, so Perseus provides the snoop commands to help you. There are three:

$ perseus snoop build

will run the build process directly, with no frills, allowing you to see all the output of your own code (Perseus performs no logging)



$ perseus snoop wasm-build

will run the Wasm build process, which is just compiling your code to Wasm (you probably won't use this unless you're having Wasm-specific compiler errors)


$ perseus snoop serve

will run the server directly, allowing you to see any dbg!() calls or the like that occur on requests

https://framesurge.sh/perseus/en-US/docs/0.4.x/fundamentals/debugging

Debugging | Perseus Docs

 

 

 

https://docs.rs/perseus/latest/perseus/

perseus - Rust

 

 

 

 

homepage만들고 얼마나 잘 만들었나 점수 체크하기

https://pagespeed.web.dev/

PageSpeed Insights

 

 

 

https://framesurge.sh/perseus/en-US/

Perseus

 

---