prep for preview release

Cargo.toml

@@ -34,7 +34,6 @@ members = [
   # libraries
   "meta",
   "router",
-  "is_server",
   "router_macro",
   "any_error",
 ]

is_server/Cargo.toml

@@ -1,8 +0,0 @@
-[package]
-name = "is_server"
-edition = "2021"
-version.workspace = true
-
-# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
-
-[dependencies]

is_server/src/lib.rs

@@ -1,14 +0,0 @@
-pub fn add(left: usize, right: usize) -> usize {
-    left + right
-}
-
-#[cfg(test)]
-mod tests {
-    use super::*;
-
-    #[test]
-    fn it_works() {
-        let result = add(2, 2);
-        assert_eq!(result, 4);
-    }
-}

or_poisoned/Cargo.toml

@@ -1,6 +1,12 @@
 [package]
 name = "or_poisoned"
 edition = "2021"
-version.workspace = true
+version = "0.1.0"
+authors = ["Greg Johnston"]
+license = "MIT"
+readme = "../README.md"
+repository = "https://github.com/leptos-rs/leptos"
+description = "Unwrap std lock guards in a semantic way."
+rust-version.workspace = true
 
 [dependencies]

or_poisoned/README.md

@@ -0,0 +1,16 @@
+Provides a simple trait that unwraps the locks provide by [`std::sync::RwLock`].
+
+In every case, this is the same as calling `.expect("lock poisoned")`. However, it
+does not use `.unwrap()` or `.expect()`, which makes it easier to distinguish from
+other forms of unwrapping when reading code.
+
+```rust
+use or_poisoned::OrPoisoned;
+use std::sync::RwLock;
+
+let lock = RwLock::new(String::from("Hello!"));
+
+let read = lock.read().or_poisoned();
+// this is identical to
+let read = lock.read().unwrap();
+```