Update docs to match v3.2.0 & fix minor issues

Author: ZakaHaceCosas

.vscode/settings.json

@@ -1,5 +1,6 @@
 {
     "cSpell.words": [
+        "arithmatex",
         "ckers",
         "cking",
         "fkadd",
@@ -14,10 +15,16 @@
         "fksurrender",
         "fontawesome",
         "fuckingnode",
+        "googlecloudstorage",
         "linenums",
         "lockfiles",
+        "personaplus",
         "pkgs",
+        "preapp",
+        "sokora",
         "therf",
+        "vuelto",
+        "zaka",
         "zakahacecosas"
     ]
 }

docs/about/roadmap.md

@@ -18,8 +18,8 @@ We'll expand (and rarely, but not impossibly, shrink) this roadmap as we make pr
     - [x] `fuckingnode setup <project> <setup>` to automatically add preset `tsconfig.json`, `.gitignore`, and `fknode.yaml` files to a project.
     - [x] `fuckingnode compat` to show cross-runtime compatibility without the need to open the browser.
 - [x] Better installer
-    - [x] Revamped `.ps1` based installer for Windows.
-    - [x] New `.sh` based installed for mac and Linux.
+    - [x] Revamped `.ps1` based installer for :fontawesome-brands-windows: Windows.
+    - [x] New `.sh` based installed for :simple-apple: macOS and :simple-linux: Linux.
 - [x] Cross-runtime migration.
     - [x] Bun. Implies generating `bun.lock` in `bun.lockb` projects.
     - [x] Deno.
@@ -64,9 +64,9 @@ We'll expand (and rarely, but not impossibly, shrink) this roadmap as we make pr
     - [X] Add `launchCmd` to `fklaunch` for users to define how a project should start up.
 - [X] Better `migrate` feature.
     - [X] Respect exact versions from the previous lockfile.
-- [ ] Support `stats`' Recommended Community Standards across:
+- [X] Support `stats`' Recommended Community Standards across:
     - [X] Deno
-    - [ ] Cargo
+    - [X] Cargo
 
 ### Version 3.3
 

docs/about/social.md

@@ -7,23 +7,23 @@
 
     ---
 
-    Our community server is probably the most important part of the community. Sneak peeks, feature suggestions, and important announcements live here.
+    Our community server is probably the most important part of the community, since sneak peeks, feature suggestions, and important announcements live here.
 
     [:octicons-arrow-right-24: Join us](https://discord.gg/AA2jYAFNmq)
 
 -   :fontawesome-brands-bluesky:{ .lg .middle } __[Bluesky](https://bsky.app/profile/fknode.bsky.social)__
 
     ---
 
-    Basically Twitter but better because these guys kept their bird (I mean it's a butterfly not a bird but you get my point).
+    It's basically Twitter but better because these guys kept their bird (I mean it's a butterfly and not a bird but you get my point). We post updates and tips here.
 
     [:octicons-arrow-right-24: Follow us](https://bsky.app/profile/fknode.bsky.social)
 
 -   :fontawesome-brands-twitter:{ .lg .middle } __[Twitter](https://x.com/FuckingNode)__
 
     ---
 
-    Users who refer to this platform as "X" instead of "Twitter" will be prohibited from using FuckingNode.
+    Users who refer to this platform as "X" instead of "Twitter" will be prohibited from using FuckingNode. We make here the same posts we make on Bluesky, literally.
 
     [:octicons-arrow-right-24: Follow us](https://x.com/FuckingNode)
 

docs/learn/audit.md

@@ -3,7 +3,7 @@
 An attempt to make security reports easier.
 
 !!! danger "Outdated"
-    **This section will not be updated until V3.3.** To prevent updates from taking ages, as we've recently planned a full rewrite of this feature, we will not waste our time on fixing a feature that is not considered stable for use anyway.
+    **This section will not be updated until V3.3**. To prevent updates from taking ages, as we've recently planned a full rewrite of this feature, we will not waste our time on fixing a feature that is not considered stable for use anyway.
     **Avoid using audit as of now.**
 
 !!! danger "Work in Progress feature"

docs/manual/commit.md

@@ -33,7 +33,7 @@ You'll see a confirmation like this one, showing what will be made:
 Run deno task test
 If everything above went alright, commit 0 file(s) to branch v3 with message "test"
 
-- all of this at @zakahacecosas/fuckingnode@3.0.0-alpha.3 C:\Users\Zaka\FuckingNode
+- all of this at @zakahacecosas/fuckingnode@3.2.0 C:\Users\Zaka\FuckingNode
 Confirm? [y/N]
 ```
 

docs/manual/configuration.md

@@ -36,7 +36,7 @@ fuckingnode manager add --self
 
 This is our recommended way, as you can run it right after running `npm init` and you don't have to type a long folder name.
 
-**3 /** You also can waste your time opening the config file. It's a plain text file that stores absolute paths separated by line breaks. On Windows it lives at your local `%APPDATA%`, and on Linux & mac it lives on `HOME` (or `XDG_CONFIG_HOME`). It looks kinda like this:
+**3 /** You also can waste your time opening the config file. It's a plain text file that stores absolute paths separated by line breaks. On :fontawesome-brands-windows: Windows it lives at your local `%APPDATA%`, and on :simple-linux: Linux & :simple-apple: macOS it lives on `HOME` (or `XDG_CONFIG_HOME`). It looks kinda like this:
 
 ```txt title="fuckingnode-motherfuckers.txt" linenums="1"
 C:\Users\JohnDoe\projects\Sokora
@@ -76,15 +76,16 @@ The above would work as long as you have one added project with this package.jso
 
 ### Listing projects
 
-Just run `fuckingnode manager list`. It'll beautifully show you all of your projects in a `name@version path` format, kinda like this (but with colors and cool stuff):
+Just run `fuckingnode manager list`. It'll beautifully show you all of your projects in a `name@version path` format, like below, but with colors and cool stuff.
 
 ```bash
 💡 Here are the m*therf*ckers you added so far:
 
-personaplus@0.0.6-preapp.29 C:\\Users\\Zaka\\personaplus
-@zakahacecosas/fuckingnode@3.1.0 C:\\Users\\Zaka\\FuckingNode
-@zakahacecosas/string-utils@1.11.0 C:\\Users\\Zaka\\string-utils
-...
+sokora@0.3.0 /home/zaka/Code/Sokora
+vuelto.pp.ua@v1.1.2 /home/zaka/Code/vuelto
+personaplus-website@0.1.0 /home/zaka/Code/personaplus-website
+personaplus@0.0.6-preapp.30 /home/zaka/Code/personaplus
+@zakahacecosas/fuckingnode@3.1.1 /home/zaka/Code/FuckingNode
 ```
 
 Later on we'll see how to "ignore" projects; here we'll tell you that you can pass `--ignored` to only list ignored projects, or `--alive` to only list non-ignored projects. If you try to mix both flags to create a loophole and break the matrix, you won't break anything; the flag you write first will overrule the second one.
@@ -128,7 +129,7 @@ fuckingnode settings change update-freq 15
 
 ### Additional settings commands
 
-Settings includes an additional `flush` command, that takes a `<file>` (`logs`, `updates`, `projects`, or `all`) as an argument, removing that from F\*ckingNode's configuration. Removing `logs` is particularly recommended. Removals of `projects` and `all` are discouraged - by the way, yes, we store all logs in a `.log` file, it lives in `%APPDATA%/FuckingNode` on Windows and `/home/USER/.config/FuckingNode` on Linux & macOS.
+Settings includes an additional `flush` command, that takes a `<file>` (`logs`, `updates`, `projects`, or `all`) as an argument, removing that from F\*ckingNode's configuration. Removing `logs` is particularly recommended. Removals of `projects` and `all` are discouraged - by the way, yes, we store all logs in a `.log` file, it lives in `%APPDATA%/FuckingNode` on :fontawesome-brands-windows: Windows and `/home/USER/.config/FuckingNode` on :simple-linux: Linux & :simple-apple: macOS.
 
 There's another settings command, `settings repair`. It simply resets settings to defaults.
 

docs/manual/fknode-yaml.md

@@ -154,8 +154,43 @@ Specifies a task to be executed upon running the `commit` command.
   commitCmd: "commit" # equals "npm run commit"
   ```
 
+## launchCmd
+
+Specifies a task to be executed upon running the `launch` command. Only used for NodeJS and Bun, analog to [`launchFile`](#launchfile) in other runtimes.
+
+- **Type**: `string`
+- **Example**:
+
+  ```yaml
+  launchCmd: "start" # equals "npm run start"
+  ```
+
+## launchFile
+
+Specifies a path to a code file to be executed upon running the `launch` command. Only used for DenoJS, Cargo and Golang, analog to [`launchCmd`](#launchcmd) in other runtimes.
+
+- **Type**: `string`
+- **Example**:
+
+  ```yaml
+  launchFile: "src/main.go" # runs "<PROJECT-ROOT>/src/main.go"
+  ```
+
+## launchWithUpdate
+
+Specifies whether to update a project's dependencies upon running the `launch` command. False by default.
+
+- **Type**: `boolean`
+- **Example**:
+
+  ```yaml
+  launchWithUpdate: true # updates deps of a project when launching it
+  ```
+
 ---
 
+## Full sample
+
 This is an example of a full `fknode.yaml` file.
 
 ```yaml
@@ -177,10 +212,12 @@ flagless:
 releaseCmd: "release"
 releaseAlwaysDry: true
 commitCmd: "commit"
+launchCmd: "dev"
+launchWithUpdate: true
 ```
 
 ---
 
-You've now learn how to configure each project to your liking.
+You've now learnt how to configure each project to your liking.
 
 Next: Kickstart - Now proceed a bunch of extra features from the CLI to enhance productivity; kickstart is the first one.

docs/manual/index.md

@@ -25,6 +25,10 @@ For further learning:
 
 ## TL;DR for getting started as soon as possible
 
+### Step 0
+
+Install it for your platform following the instructions [here](./install.md) (just like any professional tool, installation is as easy as running one CLI command).
+
 ### Step 1
 
 Add your projects to FuckingNode's project list. This is done manually with the `fuckingnode manager add <path>` (or `fkadd <path>`) command. `<path>` can be any file path, or `--self` to use the CWD.

docs/manual/install.md

@@ -4,23 +4,23 @@ First thing first, install the CLI:
 
 ## Standard installation
 
-### Microsoft Windows
+### :fontawesome-brands-windows: Microsoft Windows
 
 Copy and paste the following code in a terminal session.
 
 ```powershell
 powershell -c "irm fuckingnode.github.io/install.ps1 | iex"
 ```
 
-### Linux and macOS
+### :simple-linux: Linux and :simple-apple: macOS
 
 Copy and paste the following code in a terminal session.
 
 ```bash
 curl -fsSL fuckingnode.github.io/install.sh | bash
 ```
 
-### Nix / NixOS
+### :simple-nixos: Nix / NixOS
 
 !!! warning
     ARM (`aarch64-linux`) support is available, but NOT tested!
@@ -41,7 +41,7 @@ Then, add this to your system packages:
 inputs.fuckingnode.packages."${pkgs.system}".default;
 ```
 
-## Compile from source
+## :simple-deno: Compile from source
 
 For contributors and nerds who clone the entire source just to change one line they don't like, compiling is extremely easy:
 

docs/manual/launch.md

@@ -2,7 +2,7 @@
 
 > `fuckingnode launcher <project>`, or `fklaunch <project>`
 
-The `launch` command is a simple extra command that automatically launches your favorite editor with a project open and updates your dependencies. It can take a project's name from the `package.json` / `deno.json` / `Cargo.toml`, so it's as simple as doing `fklaunch my-project`.
+The `launch` command is a command that automatically launches your favorite editor with a project open, and automatically runs a "launch task", e.g. `npm run start`. It can also auto-update your dependencies on launch. It can take a project's name from the `package.json` / `deno.json` / `Cargo.toml`, so it's as simple as doing `fklaunch my-project`.
 
 ## Usage
 
@@ -14,6 +14,8 @@ fuckingnode launch < PROJECT >
 
 `PROJECT` is obvious and mandatory. It can be a relative file path, absolute file path, or the project's name as mentioned before.
 
+By default it just launches your favorite editor with your project opened. For us to be able to run a task or update your dependencies, [setup those features from the project's `fknode.yaml` file](./fknode-yaml.md#launchcmd).
+
 ---
 
 You've now learnt how to speed up launching your projects.