format: prettier --write .

Author: ryan4yin

README.md

@@ -8,13 +8,15 @@ you've come to the right place!
 An unofficial and opinionated NixOS & Flakes :book: for beginners:
 https://nixos-and-flakes.thiscute.world/
 
-### Author-Maintained Versions: 
-* **English Version**: https://nixos-and-flakes.thiscute.world/
-* **中文版**: https://nixos-and-flakes.thiscute.world/zh/
+### Author-Maintained Versions:
+
+- **English Version**: https://nixos-and-flakes.thiscute.world/
+- **中文版**: https://nixos-and-flakes.thiscute.world/zh/
 
 ### Community-Maintained Versions:
-* **Versão em Português**: https://nixos-and-flakes.ieda.me/
-* **日本語版**: https://nixos-and-flakes-ja.hayao0819.com/
+
+- **Versão em Português**: https://nixos-and-flakes.ieda.me/
+- **日本語版**: https://nixos-and-flakes-ja.hayao0819.com/
 
 > If you're using macOS,
 > [ryan4yin/nix-darwin-kickstarter](https://github.com/ryan4yin/nix-darwin-kickstarter)
@@ -88,6 +90,7 @@ who already contributed to this project!
 Yin is licensed under [CC BY-SA 4.0](./LICENSE.md)
 
 [^1]: [Flakes - NixOS Wiki](https://wiki.nixos.org/wiki/Flakes)
+
 [^2]:
     [Flakes are such an obviously good thing](https://grahamc.com/blog/flakes-are-an-obviously-good-thing/)
 

docs/.vitepress/config/index.ts

@@ -1,8 +1,7 @@
-import { defineConfig } from 'vitepress'
-import { shared } from './shared'
-import { en } from './en'
-import { zh } from './zh'
-
+import { defineConfig } from "vitepress"
+import { shared } from "./shared"
+import { en } from "./en"
+import { zh } from "./zh"
 
 export default defineConfig({
   ...shared,
@@ -12,13 +11,13 @@ export default defineConfig({
     "en/:rest*": ":rest*",
   },
   locales: {
-    root: { 
-      label: 'English',
-      ...en 
+    root: {
+      label: "English",
+      ...en,
     },
     zh: {
-      label: '简体中文', 
-      ...zh
+      label: "简体中文",
+      ...zh,
     },
     pt: {
       label: "Português",
@@ -45,14 +44,13 @@ export default defineConfig({
   //   },
   //
   //   // Languages maintained by the original author
-  //   en: { 
+  //   en: {
   //     label: 'English',
   //   link: "https://nixos-and-flakes.thiscute.world/",
   //   },
   //   zh: {
-  //     label: '简体中文', 
+  //     label: '简体中文',
   //     link: "https://nixos-and-flakes.thiscute.world/zh/",
   //   },
   // },
 })
-

docs/.vitepress/config/shared.ts

@@ -1,4 +1,4 @@
-import { createRequire } from 'module'
+import { createRequire } from "module"
 import { generateSitemap as sitemap } from "sitemap-ts"
 import { PageData, defineConfig } from "vitepress"
 
@@ -43,14 +43,17 @@ export const shared = defineConfig({
   },
 
   head: [
-    ["link", { rel: "icon", href: "/favicon-16x16.png", sizes: "16x16"  }],
-    ["link", { rel: "icon", href: "/favicon-32x32.png", sizes: "32x32"  }],
+    ["link", { rel: "icon", href: "/favicon-16x16.png", sizes: "16x16" }],
+    ["link", { rel: "icon", href: "/favicon-32x32.png", sizes: "32x32" }],
     // Google Search and Android Chrome
     ["link", { rel: "icon", href: "/favicon-96x96.png", sizes: "96x96" }],
     ["link", { rel: "icon", href: "/web-app-manifest-192x192.png", sizes: "192x192" }],
     ["link", { rel: "icon", href: "/web-app-manifest-512x512.png", sizes: "512x512" }],
     // For Apple iPhone/iPad
-    ["link", { rel: "apple-touch-icon", href: "/apple-touch-icon.png", sizes: "180x180" }],
+    [
+      "link",
+      { rel: "apple-touch-icon", href: "/apple-touch-icon.png", sizes: "180x180" },
+    ],
 
     // site.manifest
     ["link", { rel: "manifest", href: "/site.webmanifest" }],

docs/en/best-practices/accelerating-dotfiles-debugging.md

@@ -40,8 +40,8 @@ in
 
 After modifying the configuration, run `sudo nixos-rebuild switch` (or
 `home-manager switch` if you are using Home Manager standalone) to apply the changes. From
-then on, any modifications you make to `~/nix-config/home/nvim` or `~/nix-config/home/doom` will be
-immediately observed by Neovim/Emacs.
+then on, any modifications you make to `~/nix-config/home/nvim` or
+`~/nix-config/home/doom` will be immediately observed by Neovim/Emacs.
 
 This way, you can manage all your Dotfiles using a single nix-config repository, while
 frequently modified non-Nix configurations can take effect quickly, unaffected by Nix.

docs/en/best-practices/nix-path-and-flake-registry.md

@@ -38,10 +38,10 @@ then downloads the repository, locates the `flake.nix` within, and runs the corr
 
 The roles of `NIX_PATH` and the Flake Registry have been explained earlier. In daily use,
 we typically want the `nixpkgs` used in commands like `nix repl '<nixpkgs>'`,
-`nix run nixpkgs#ponysay hello` to match the system's `nixpkgs`. This is done
-by default as of [NixOS 24.05][automatic flake registry]. Also, although
-`nix-channel` can coexist with the Flakes feature, in practice, Flakes can
-completely replace it, so we can also disable it.
+`nix run nixpkgs#ponysay hello` to match the system's `nixpkgs`. This is done by default
+as of [NixOS 24.05][automatic flake registry]. Also, although `nix-channel` can coexist
+with the Flakes feature, in practice, Flakes can completely replace it, so we can also
+disable it.
 
 [automatic flake registry]: https://github.com/NixOS/nixpkgs/pull/254405
 

docs/en/best-practices/run-downloaded-binaries-on-nixos.md

@@ -27,7 +27,7 @@ add the following code to one of your Nix modules:
     (let base = pkgs.appimageTools.defaultFhsEnvArgs; in
       pkgs.buildFHSUserEnv (base // {
       name = "fhs";
-      targetPkgs = pkgs: 
+      targetPkgs = pkgs:
         # pkgs.buildFHSUserEnv provides only a minimal FHS environment,
         # lacking many basic packages needed by most software.
         # Therefore, we need to add them manually.

docs/en/nix-store/add-binary-cache-servers.md

@@ -37,9 +37,9 @@ In Nix, you can configure cache servers using the following options:
       the build process of a certain library, they must take on the corresponding security
       risks and decide whether to add the public key of that cache server to
       `trusted-public-keys`. To completely solve this trust issue, Nix has introduced the
-      experimental feature [ca-derivations](https://wiki.nixos.org/wiki/Ca-derivations), which
-      does not depend on `trusted-public-keys` for signature verification. Interested
-      users can explore it further.
+      experimental feature [ca-derivations](https://wiki.nixos.org/wiki/Ca-derivations),
+      which does not depend on `trusted-public-keys` for signature verification.
+      Interested users can explore it further.
 
 You can configure the `substituters` and `trusted-public-keys` parameters in the following
 ways:

docs/en/nixos-with-flakes/downgrade-or-upgrade-packages.md

@@ -104,7 +104,12 @@ submodule. Here's an example of a Home Manager submodule:
 
 ## Pinning a package version with an overlay
 
-The above approach is perfect for application packages, but sometimes you need to replace libraries used by those packages. This is where [Overlays](../nixpkgs/overlays.md) shine! Overlays can edit or replace any attribute of a package, but for now we'll just pin a package to a different nixpkgs version. The main disadvantage of editing a dependency with an overlay is that your Nix installation will recompile all installed packages that depend on it, but your situation may require it for specific bug fixes.
+The above approach is perfect for application packages, but sometimes you need to replace
+libraries used by those packages. This is where [Overlays](../nixpkgs/overlays.md) shine!
+Overlays can edit or replace any attribute of a package, but for now we'll just pin a
+package to a different nixpkgs version. The main disadvantage of editing a dependency with
+an overlay is that your Nix installation will recompile all installed packages that depend
+on it, but your situation may require it for specific bug fixes.
 
 ```nix
 # overlays/mesa.nix

docs/en/nixos-with-flakes/introduction-to-flakes.md

@@ -85,29 +85,31 @@ them with the corresponding New CLI commands (except for `nix-collect-garbage`,
 is currently no alternative for this command):
 
 1. `nix-channel`: `nix-channel` manages versions of inputs like nixpkgs through
-   stable/unstable channels, similar to the package lists used by other package
-   management tools such as apt/yum/pacman. This is what traditionally provides
-   `<nixpkgs>` in the Nix language.
-   1. In Flakes, the functionality of `nix-channel` is replaced by
-      the Flake Registry (`nix registry`) for providing "some unspecified global
-      version of nixpkgs" for interactive CLI usage (e.g. `nix run nixpkgs#hello`).
-      When using a `flake.nix`, input versions are managed in the flake itself.
-   2. Flakes use the `inputs` section in `flake.nix` to manage
-      versions of nixpkgs and other inputs in each Flake instead of using
-      global state.
+   stable/unstable channels, similar to the package lists used by other package management
+   tools such as apt/yum/pacman. This is what traditionally provides `<nixpkgs>` in the
+   Nix language.
+   1. In Flakes, the functionality of `nix-channel` is replaced by the Flake Registry
+      (`nix registry`) for providing "some unspecified global version of nixpkgs" for
+      interactive CLI usage (e.g. `nix run nixpkgs#hello`). When using a `flake.nix`,
+      input versions are managed in the flake itself.
+   2. Flakes use the `inputs` section in `flake.nix` to manage versions of nixpkgs and
+      other inputs in each Flake instead of using global state.
 2. `nix-env`: `nix-env` is a core command-line tool for classic Nix used to manage
    software packages in the user environment.
+
    1. It installs packages from the data sources added by `nix-channel`, causing the
       installed package's version to be influenced by the channel. Packages installed with
       `nix-env` are not automatically recorded in Nix's declarative configuration and are
       completely independent of its control, making them challenging to reproduce on other
-      machines. Upgrading packages installed by `nix-env` is slow and may
-      produce unexpected results because the attribute name where the package
-      was found in nixpkgs is not saved.
+      machines. Upgrading packages installed by `nix-env` is slow and may produce
+      unexpected results because the attribute name where the package was found in nixpkgs
+      is not saved.
 
       Therefore, it is not recommended to use this command directly.
+
    2. The corresponding command in the New CLI is `nix profile`. Personally, I don't
       recommend it for beginners.
+
 3. `nix-shell`: `nix-shell` creates a temporary shell environment, which is useful for
    development and testing.
    1. New CLI: This tool is divided into three sub-commands: `nix develop`, `nix shell`,
@@ -126,6 +128,7 @@ is currently no alternative for this command):
       [Try to explain nix commands](https://qiita.com/Sumi-Sumi/items/6de9ee7aab10bc0dbead?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en).
 
 [^1]: [Flakes - NixOS Wiki](https://wiki.nixos.org/wiki/Flakes)
+
 [^2]:
     [Flakes are such an obviously good thing](https://grahamc.com/blog/flakes-are-an-obviously-good-thing/)
 

docs/en/nixos-with-flakes/nixos-flake-configuration-explained.md

@@ -182,5 +182,3 @@ source code, and study its implementation.
   https://github.com/NixOS/nixpkgs/blob/nixos-25.05/lib/modules.nix#L122-L184
 [nixpkgs/nixos-25.05/nixos/doc/manual/development/option-types.section.md#L268-L275]:
   https://github.com/NixOS/nixpkgs/blob/nixos-25.05/nixos/doc/manual/development/option-types.section.md?plain=1#L268-L275
-
-