rename native:serve to native:run

Author: gwleuverink

resources/views/docs/desktop/2/getting-started/debugging.md

@@ -19,7 +19,7 @@ This means that while some issues can be solved within NativePHP it's also very
 ### The layers
 
 - Your application, built on Laravel, using your local installations of PHP & Node.
-- NativePHP's development tools (`native:serve` and `native:build`) manage the Electron/Tauri build processes - this is
+- NativePHP's development tools (`native:run` and `native:build`) manage the Electron/Tauri build processes - this is
   what creates your Application Bundle.
 - NativePHP moves the appropriate version of a statically-compiled binary of PHP into your application's bundle - when
   your app boots, it's _this_ version of PHP that is being used to execute your PHP code, not your system's version of
@@ -51,7 +51,7 @@ runs in either a dev build or a prod build.
 Having a clear understanding about what context you're in when issues occur will help you to solve the problem faster.
 
 ### Verbose output
-Use `-v`, `-vv` or `-vvv` when running `native:serve` or `native:build` as this will provide more detail as to what's 
+Use `-v`, `-vv` or `-vvv` when running `native:run` or `native:build` as this will provide more detail as to what's 
 happening at each stage of a process.
 
 ### Check the logs

resources/views/docs/desktop/2/getting-started/development.md

@@ -6,21 +6,21 @@ order: 300
 ## Development
 
 ```shell
-php artisan native:serve
+php artisan native:run
 ```
 
 NativePHP isn't prescriptive about how you develop your application. You can build it in the way you're most comfortable
 and familiar with, just as if you were building a traditional web application.
 
 The only difference comes in the feedback cycle. Instead of switching to and refreshing your browser, you'll need to
-be serving your application using `php artisan native:serve` and refreshing (and in some cases restarting) your
+be serving your application using `php artisan native:run` and refreshing (and in some cases restarting) your
 application to see changes.
 
 This is known as 'running a dev build'.
 
-### What does the `native:serve` command do?
+### What does the `native:run` command do?
 
-The `native:serve` command runs the Electron/Tauri 'debug build' commands, which build your application with various
+The `native:run` command runs the Electron 'debug build' commands, which build your application with various
 debug options set to help make debugging easier, such as allowing you to show the Dev Tools in the embedded web view.
 
 It also keeps the connection to the terminal open so you can see and inspect useful output from your app, such as logs,
@@ -34,7 +34,7 @@ A major part of the build process, even for debug builds, involves _copying_ you
 build environment. This means that changes you make to your application code _will not_ be reflected in your running
 application until you restart it.
 
-You can stop the `native:serve` command by pressing `Ctrl-C` on your keyboard in the terminal window it's running in.
+You can stop the `native:run` command by pressing `Ctrl-C` on your keyboard in the terminal window it's running in.
 It will also terminate when you quit your application.
 
 ## Hot Reloading
@@ -49,7 +49,7 @@ If you're using Vite, hot reloading will just work inside your app as long as yo
 
 You can do this easily in Blade using the `@@vite` directive.
 
-Then, in a separate terminal session to your `php artisan native:serve`, from the root folder of your application, run:
+Then, in a separate terminal session to your `php artisan native:run`, from the root folder of your application, run:
 
 ```shell
 npm run dev
@@ -61,7 +61,7 @@ Which files trigger reloads will depend on your Vite configuration.
 
 ### `composer native:dev`
 
-You may find the `native:dev` script convenient. By default, it is setup to run both `native:serve` and `npm run dev`
+You may find the `native:dev` script convenient. By default, it is setup to run both `native:run` and `npm run dev`
 concurrently in a single command:
 
 ```shell
@@ -99,7 +99,7 @@ For more details, see the [Databases](/docs/digging-deeper/databases) section.
 
 ## App Icon
 
-The `native:serve` and `native:build` commands look for the following icon files when building your application:
+The `native:run` and `native:build` commands look for the following icon files when building your application:
 
 - `public/icon.png` - your main icon, used on the Desktop, Dock and app switcher.
 - `public/icon.ico` - if it exists, it is used as an icon file for Windows (optional).

resources/views/docs/desktop/2/getting-started/installation.md

@@ -68,7 +68,7 @@ which need addressing before you can run your app natively, and may be trickier
 Once you're ready:
 
 ```shell
-php artisan native:serve
+php artisan native:run
 ```
 
 And that's it! You should now see your Laravel application running in a native desktop window. 🎉

resources/views/docs/desktop/2/getting-started/upgrade-guide.md

@@ -54,8 +54,8 @@ v2 drops support for macOS **_Catalina_** and **_Big Sur_**. This change comes f
 
 ## Renamed `native:serve` command
 
-The `artisan native:serve` command has been renamed to `artisan native:dev` for better symmetry with the mobile package.
-Please update the `composer native:dev` command to use the new name.
+The `artisan native:serve` command has been renamed to `artisan native:run` for better symmetry with the mobile package.
+Please update the `composer native:dev` script to reference the new run command.
 
 ## Security defaults