Update to V4.1 + Fixes + Document migrate (it never was 😭)

Author: ZakaHaceCosas

docs/learn/notifications.md

@@ -0,0 +1,10 @@
+# System notifications
+
+By default, `clean`, `migrate`, and `kickstart`, which are considered features that _can_ take a long time, will send a system UI notification if they _do_ take long. Unless you're on DND it should sound - which is the point of it. They're sent so you can safely move away from the terminal and know when we're done, so you can get back to whatever's next as soon as possible.
+
+These notifications are fired if the running task took more than 30 seconds to complete. This threshold can be disabled, so they're shown even if it takes 1 second. In future versions you'll be able to customize the threshold.
+
+Notifications are enabled by default, but can be disabled if you don't like them.
+
+!!! warning Support for Linux
+    On Linux, it's assumed that `notify-send` is installed. If not, notifications simply won't be sent, without a warning.

docs/manual/build.md

@@ -40,7 +40,7 @@ There's nothing more to configure. It's a relatively simple automation.
 
 ### What to expect
 
-Progress with all commands will be printed step by step.
+Progress with all commands will be printed step by step. Note that output is not shown live, it gets printed all at once the moment the command finishes execution.
 
 ```bash
 ✔ There we go, time to build <project name here>

docs/manual/configuration.md

@@ -107,35 +107,39 @@ As most apps, we offer settings you can tweak. We use default values that should
 
 Currently supported settings are the following them. Change them with `settings change <KEY> <value>`
 
-| KEY | Value Type | Description | Notes |
-| :--- | ---: | :--- | ---: |
-| `defaultIntensity` | `normal`, `hard`, `hard-only`, `maxim`, or `maxim-only` | Changes the default intensity for the `clean` command. | / |
-| `updateFreq` | A fixed number | Changes how frequently (in DAYS) the CLI sends an HTTP request for updates. | We recommend setting it to a high value as we don't frequently update, so you can save up those HTTP requests. |
-| `flushFreq` | A fixed number | Changes how frequently (in DAYS) the CLI removes the `.log` file to save up space. | Cannot be disabled, setting it to `0` will make it auto-flush each time. |
-| `favEditor`  | `vscode`, `sublime`, `emacs`, `atom`, `vscodium`, `notepad++` | Your favorite code editor. Used by `kickstart`. | / |
+| KEY | Value Type | Description |
+| :--- | :--- | ---: |
+| `defaultIntensity` | `normal`, `hard`, `hard-only`, `maxim`, or `maxim-only` | Changes the default intensity for the `clean` command. |
+| `updateFreq` | A fixed number | Changes how frequently (in DAYS) the CLI sends an HTTP request for updates. We recommend setting it to a high value as we don't frequently update. |
+| `flushFreq` | A fixed number | Changes how frequently (in DAYS) the CLI removes the `.log` file to save up space. Cannot be disabled, setting it to `0` will make it auto-flush each time. |
+| `favEditor`  | `vscode`, `sublime`, `emacs`, `atom`, `vscodium`, `notepad++` | Your favorite code editor. Used by `kickstart` and `launch`. |
+| `showNotifications`  | `true`, `false` | Whether to [use system notifications](../learn/notifications.md). Highly recommended |
+| `thresholdNotifications`  | `true`, `false` | Enabled by default, makes system notifications only fire up if the task to be notified about takes less than 30 seconds. |
 
 ### View current settings
 
 To view your current settings, run `fuckingnode settings` with no args. You should see something like this:
 
-```bash
+```txt
 💡 Your current settings are:
 ---
-Update frequency: Each 69 days. updateFreq
-Default cleaner intensity: hard. defaultIntensity
-Favorite editor: vscodium. favEditor
-Auto-flush log file frequency: Each 13 days. flushFreq
+Check for updates             | Every 5 days. updateFreq        
+Default cleaner intensity     | normal. defaultIntensity        
+Favorite code editor          | vscode. favEditor
+Auto-flush log file           | Every 14 days. flushFreq        
+Send system notifications     | Enabled. showNotifications      
+Threshold notifications (30") | Disabled. thresholdNotifications
 ```
 
-As you can see, you're shown at the end the key used to change a setting.
+As you can see, you're shown at the end the key used to change a setting (it appears _italic_ in your terminal, if supported).
 
 ### Change settings
 
-To change them, execute `fuckingnode settings change (SETTING) (VALUE)`, for example:
+To change them, execute `fuckingnode settings change (KEY) (VALUE)`, for example:
 
 ```bash
-fuckingnode settings change default-int "hard"
-fuckingnode settings change update-freq 15
+fuckingnode settings change defaultIntensity "hard"
+fuckingnode settings change updateFreq 15
 ```
 
 ### Additional settings commands

docs/manual/index.md

@@ -12,8 +12,10 @@ These are links to individual pages. For the full manual, click the first one, t
 - [Individual project config (fknode.yaml)](fknode-yaml.md)
 - [Feature - Kickstart](kickstart.md)
 - [Feature - Commit](commit.md)
+- [Feature - Build](build.md)
 - [Feature - Release](release.md)
 - [Feature - Launch](launch.md)
+- [Feature - Migrate](migrate.md)
 - [Feature - Setup](setup.md)
 - [Feature - Stats](stats.md)
 - [Feature - Surrender](surrender.md)

docs/manual/kickstart.md

@@ -9,6 +9,8 @@ The `kickstart` command is an extra command that increases your productivity by
 - Launches your favorite code editor (as defined by your user settings).
 - Adds the project to the FuckingNode list.
 
+Plus, **if it takes long, you'll receive a [system notification](../learn/notifications.md) once done,** so if it's a large repo you can just switch tabs and focus on something else, and get notified once ready so you can get to coding.
+
 ## Usage
 
 Just run the following:

docs/manual/launch.md

@@ -1,6 +1,6 @@
 # Using FuckingNode: Launch a project
 
-> `fuckingnode launcher <project>`, or `fklaunch <project>`
+> `fuckingnode launch <project>`, or `fklaunch <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`.
 
@@ -20,4 +20,4 @@ By default it just launches your favorite editor with your project opened. For u
 
 You've now learnt how to speed up launching your projects.
 
-Next: Setup - How to quickly get text-config files ready.
+Next: Migrate - How to escape npm.

docs/manual/migrate.md

@@ -0,0 +1,27 @@
+# Using FuckingNode: Migrate a project
+
+> `fuckingnode migrate <project> <target>`, or `fklaunch <project> <target>`
+
+The `migrate` command automatically migrates your project from one JS stack to another. For example, from npm to Bun, or from npm to pnpm, or from npm to anything better.
+
+It doesn't do any migration _per se_, it relies on package managers knowing how to manage that (which is usually the case). Its purpose is to automate the process, since a migration involves several steps (updating lockfiles, removing node_modules, installing, removing old lockfile...).
+
+As this can take time, **if it takes long, you'll receive a [system notification](../learn/notifications.md) once done,** so you can just switch tabs and focus on something else, and get notified once ready so you can get back to coding.
+
+## Usage
+
+Just run the following:
+
+```bash
+fuckingnode migrate <TARGET> <PROJECT>
+```
+
+`TARGET` is the target package manager (the one to migrate to), can be either npm or pnpm or yarn or deno or bun. `PROJECT` is optional, specifies what project to be migrated, if not provided the CWD is used.
+
+We'll tell you step by step what are we doing. Previous lockfile will be copied to a `.bak` file.
+
+---
+
+You've now learnt how to escape npm.
+
+Next: Setup - How to quickly get text-config files ready.

docs/manual/usage.md

@@ -11,11 +11,13 @@ The core idea of FuckingNode is to automate cleanup of your NodeJS projects. On
 The `fuckingnode clean` command is the base utility of the app. It accepts the following (all optional) arguments:
 
 ```bash
-fuckingnode clean <PROJECT | --> <INTENSITY | --> [--update] [--lint] [--pretty] [--destroy] [--verbose] [--commit]
+fuckingnode clean <PROJECT | --> <INTENSITY | --> [--update] [--lint] [--pretty] [--destroy] [--commit]
 ```
 
 When executed with no arguments, it'll do a cleanup using the default intensity (which is `normal` and can be changed from the [settings](configuration.md#settings)) across all of your projects.
 
+It'll iterate through all of your projects and clean them, showing status updates one by one in the terminal. Once it ends, a report is shown, telling how much time did it take us to clean each individual project. **You'll receive a [system notification](../learn/notifications.md) once done,** so you can switch tabs and focus on something else - you'll know when to come back.
+
 ## Cleaner intensities, explained
 
 There are five (well, three in reality) intensities available:
@@ -133,7 +135,7 @@ Some of these features depend on `fknode.yaml` configuration, [as noted above](#
 
 !!! info "About errors"
 
-    Any error from additional tasks will fail silently; this means they won't stop the execution flow and no logs will be made. However, since the CLI shows command output live, errors will likely be shown in there.
+    Any error from additional tasks will fail silently; this means they won't stop the execution flow and no logs will be made. Error logs are dumped into a log file; you're shown the path whenever an error of this kind happens.
 
 ### Linting your code: `--lint`
 
@@ -239,12 +241,6 @@ To override it, do the same as with the linter and prettifier, but setting the `
 updateCmdOverride: "update"
 ```
 
-## Additional info
-
-### Show additional info during cleanup
-
-There's a `--verbose` flag that can be passed to `fuckingnode clean`. It'll show the real output of all commands that are being executed, begin and end timestamps for the cleanup process, plus a report showing how much time did it take us to clean each individual project.
-
 ---
 
 You've now learnt how to use the base cleaner.

mkdocs.yml

@@ -27,6 +27,7 @@ nav:
           - Feature - Build: "manual/build.md"
           - Feature - Release: "manual/release.md"
           - Feature - Launch: "manual/launch.md"
+          - Feature - Migrate: "manual/migrate.md"
           - Feature - Setup: "manual/setup.md"
           - Feature - Stats: "manual/stats.md"
           - Feature - Surrender: "manual/surrender.md"
@@ -37,8 +38,9 @@ nav:
           - Learn: "learn/index.md"
           - Cross-runtime support: "learn/cross-runtime-support.md"
           - Error codes: "learn/errors.md"
-          - How does cleanup work under the hood: "learn/clean.md"
-          - How does audit work under the hood: "learn/audit.md"
+          - System notifications: "learn/notifications.md"
+          - How cleanup works under the hood: "learn/clean.md"
+          - How audit works under the hood: "learn/audit.md"
 
     - Roadmap: "about/roadmap.md"
     - Brand guidelines: "about/branding.md"