Set whoami default-features to false (launchbadge#2319)

* Fixed typo. (launchbadge#2156)

* Set whoami default-features to false

Otherwise, whoami pulls in web-sys, wasm-bindgen and a BUNCH of
additional dependencies. This is really unnecessary, and if
someone has an actual use case where they are attempting to connect
to postgres from a browser, well ... they've probably already been
pwned by now. If it is deemed necessary, then add an additional
activation feature for that specific slew of deps.

---------

Co-authored-by: Chris Foster <[email protected]>

Author: 2 people

Cargo.lock

@@ -61,7 +61,7 @@ smallvec = "1.7.0"
 stringprep = "0.1.2"
 thiserror = "1.0.35"
 tracing = { version = "0.1.37", features = ["log"] }
-whoami = "1.2.1"
+whoami = { version = "1.2.1", default-features = false }
 
 serde = { version = "1.0.144", optional = true }
 

sqlx-mysql/Cargo.toml

@@ -62,7 +62,7 @@ smallvec = "1.7.0"
 stringprep = "0.1.2"
 thiserror = "1.0.35"
 tracing = { version = "0.1.37", features = ["log"] }
-whoami = "1.2.1"
+whoami = { version = "1.2.1", default-features = false }
 
 serde = { version = "1.0.144", features = ["derive"] }
 serde_json = { version = "1.0.85", features = ["raw_value"] }

sqlx-postgres/Cargo.toml

@@ -733,7 +733,7 @@ macro_rules! query_file_scalar_unchecked (
 ///
 /// This is because our ability to tell the compiler to watch external files for changes
 /// from a proc-macro is very limited. The compiler by default only re-runs proc macros when
-/// one ore more source files have changed, because normally it shouldn't have to otherwise. SQLx is
+/// one or more source files have changed, because normally it shouldn't have to otherwise. SQLx is
 /// just weird in that external factors can change the output of proc macros, much to the chagrin of
 /// the compiler team and IDE plugin authors.
 ///