* Add task for cargo leptos w/ precompression
* Update makefile
* Update deps
* Serve precompressed assets
Code was taken from https://github.com/leptos-rs/cargo-leptos/pull/165#issuecomment-1647843037
Co-authored-by: Sebastian Dobe <sebastiandobe@mailbox.org>
* Dynamically compress html
* Update README
* Refactor: Format for ci
* Refactor: Replace use of format!
* Chore: Remove old build file
* Feat: Hash files
This will prevent users from using an old cached file after updates are made
* Fix: Prevent chicken & egg problem with target/site
* Refactor: Use normal cargo-leptos
---------
Co-authored-by: Sebastian Dobe <sebastiandobe@mailbox.org>
* Minor: examples/server_fns_axum FileWatcher logs errors to the console.
The cause is an assumption that the directory
./watched_files/
exits.
* chore: Now using .gitkeep to preserve directory structure.
non-serializable struct.
This prevents it from being returned in the
get_user() API, and prevents it from being unintentionally returned on any
new API the end-user may create on top of this example code.
* fix(ci): address clippy issue
* fix(ci): add missing nightly specifications
* fix(ci): set all nightly references
* chore(ci): do not lint example crates
This warning appears in the browser's console log.
```
hackernews.js:933 At src/routes/stories.rs:39:17, you are reading a resource in `hydrate` mode outside a <Suspense/> or <Transition/>. This can cause hydration mismatch errors and loses out on a significant performance optimization. To fix this issue, you can either:
1. Wrap the place where you read the resource in a <Suspense/> or <Transition/> component, or
2. Switch to using create_local_resource(), which will wait to load the resource until the app is hydrated on the client side. (This will have worse performance in most cases.)
```
This warning is seen in the browsers console window.
```
counter_isomorphic.js:1068 At src/counters.rs:138:17, you are reading a resource in `hydrate` mode outside a <Suspense/> or <Transition/>. This can cause hydration mismatch errors and loses out on a significant performance optimization. To fix this issue, you can either:
1. Wrap the place where you read the resource in a <Suspense/> or <Transition/> component, or
2. Switch to using create_local_resource(), which will wait to load the resource until the app is hydrated on the client side. (This will have worse performance in most cases.)
```
Two derived signals "value" and "error_msg" need to be wrapped in a <Suspense> block.
"value" falls back to just the initial text.
"error" uses the default fallback.
