update the hook and instructions on how to use it, tips on using modules in the scaffolded mod.nu

Author: freepicheep

README.md

@@ -105,13 +105,16 @@ source .nu_scripts/activate.nu
 When you're done, run `deactivate` (or `overlay hide activate`) to unload the module overlay.
 
 ### 2. Auto-activation Hook
-If you want nuance projects to automatically update your module path when you `cd` into their directory (and remove it when you leave), add the nuance env_change hook to your `config.nu` or `env.nu`:
 
-```bash
-# Run this and append the output to your config
-nuance hook
+If you want nuance projects to automatically update your module path when you `cd` into their directory (and remove it when you leave), add the following to your `config.nu` or `env.nu`:
+
+```nu
+mkdir ($nu.default-config-dir | path join "vendor" "autoload")
+nuance hook | save -f ($nu.default-config-dir | path join "vendor" "autoload" "nuance_hook.nu")
 ```
 
+You can also simply run these commands without adding them to your config or env file. You just won't receive any modifications of the hook until you run the commands again, but your shell startup time will be faster.
+
 > **Note**: Due to Nushell's static scoping rules, the auto-activation hook only updates `$env.NU_LIB_DIRS`. It cannot auto-import module/script commands. For automatic loading, use the manual activation approach above.
 
 ## mod.toml

src/main.rs

@@ -145,7 +145,10 @@ fn cmd_init(
     if !mod_nu.exists() {
         std::fs::write(
             &mod_nu,
-            "# Module entry point\n# Export your commands here with: export use <submodule>\n",
+            r#"# Module entry point
+            # Export your commands here with: export use <submodule>
+            # Use installed modules with: use ../.nu_modules/module-name/module-name *
+            "#,
         )?;
         eprintln!("Created {}", mod_nu.display());
     }
@@ -531,17 +534,26 @@ fn cmd_remove_global(name: String) -> Result<()> {
 }
 
 fn cmd_hook() -> Result<()> {
-    let hook_script = r#"# nuance auto-activate hook — add this to your config.nu (or env.nu)
+    let hook_script = r#"# nuance auto-activate hook
+# Add this to your Nushell environment by running:
+#   mkdir ($nu.default-config-dir | path join "vendor" "autoload")
+#   nuance hook | save -f ($nu.default-config-dir | path join "vendor" "autoload" "nuance_hook.nu")
+# Once saved, it will be automatically sourced when you start Nushell.
+# You can add the above to your config.nu if you want any updates to the hook, but that may slow start time.
+
 $env.config.hooks.env_change.PWD = (
-    $env.config.hooks.env_change.PWD | default [] | append {|before, after|
+    $env.config.hooks.env_change.PWD? | default [] | append {|before after|
+        let before = ($before | default "")
+        let after = ($after | default "")
+
         # Remove previous directory's modules/scripts if it was a nuance project
-        if ($before | path join "mod.toml" | path exists) {
+        if ($before | is-not-empty) and ($before | path join "mod.toml" | path exists) {
             let old_modules = ($before | path join ".nu_modules")
             let old_scripts = ($before | path join ".nu_scripts")
-            $env.NU_LIB_DIRS = ($env.NU_LIB_DIRS | default [] | where { |it| $it != $old_modules and $it != $old_scripts })
+            $env.NU_LIB_DIRS = ($env.NU_LIB_DIRS | default [] | where {|it| $it != $old_modules and $it != $old_scripts })
         }
         # Add new directory's modules/scripts if it is a nuance project
-        if ($after | path join "mod.toml" | path exists) {
+        if ($after | is-not-empty) and ($after | path join "mod.toml" | path exists) {
             let new_modules = ($after | path join ".nu_modules")
             let new_scripts = ($after | path join ".nu_scripts")
             if ($new_modules | path exists) and ($new_modules not-in ($env.NU_LIB_DIRS | default [])) {