fix: package name

Author: Rahmon

.github/ISSUE_TEMPLATE/1-bug-report.yml

@@ -11,7 +11,7 @@ body:
       id: faqs
       attributes:
         label: Troubleshooting
-        description: By submitting this issue, you agree that our [troubleshooting tips](https://github.com/Rahmon/wp-docker#i-am-having-issues-with-wp-local-docker-what-are-the-best-troubleshooting-techniques) have not helped resolve the issue.
+        description: By submitting this issue, you agree that our [troubleshooting tips](https://github.com/Rahmon/wpdocker#i-am-having-issues-with-wp-local-docker-what-are-the-best-troubleshooting-techniques) have not helped resolve the issue.
         options:
           - label: I have attempted to troubleshoot this already
             required: true
@@ -63,7 +63,7 @@ body:
       id: terms
       attributes:
         label: Code of Conduct
-        description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/Rahmon/wp-docker/blob/develop/CODE_OF_CONDUCT.md).
+        description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/Rahmon/wpdocker/blob/develop/CODE_OF_CONDUCT.md).
         options:
           - label: I agree to follow this project's Code of Conduct
             required: true

.github/ISSUE_TEMPLATE/2-enhancement.yml

@@ -39,7 +39,7 @@ body:
       id: terms
       attributes:
         label: Code of Conduct
-        description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/Rahmon/wp-docker/blob/develop/CODE_OF_CONDUCT.md).
+        description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/Rahmon/wpdocker/blob/develop/CODE_OF_CONDUCT.md).
         options:
           - label: I agree to follow this project's Code of Conduct
             required: true

.github/ISSUE_TEMPLATE/3-help.yml

@@ -11,7 +11,7 @@ body:
       id: faqs
       attributes:
         label: Troubleshooting
-        description: By submitting this question, you agree that our [troubleshooting tips](https://github.com/Rahmon/wp-docker#i-am-having-issues-with-wp-local-docker-what-are-the-best-troubleshooting-techniques) have not helped resolve the quesstion.
+        description: By submitting this question, you agree that our [troubleshooting tips](https://github.com/Rahmon/wpdocker#i-am-having-issues-with-wp-local-docker-what-are-the-best-troubleshooting-techniques) have not helped resolve the quesstion.
         options:
           - label: I have attempted to troubleshoot this already
             required: true
@@ -27,7 +27,7 @@ body:
       id: terms
       attributes:
         label: Code of Conduct
-        description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/Rahmon/wp-docker/blob/develop/CODE_OF_CONDUCT.md).
+        description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/Rahmon/wpdocker/blob/develop/CODE_OF_CONDUCT.md).
         options:
           - label: I agree to follow this project's Code of Conduct
             required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,5 @@
 blank_issues_enabled: false
 contact_links:
     - name: Looking for documentation?
-      url: https://github.com/Rahmon/wp-docker/#readme
+      url: https://github.com/Rahmon/wpdocker/#readme
       about: If you're looking for information on installation, global commands, environments, WP Snapshots, and related tools then check out the WP Local Docker Readme.

CHANGELOG.md

@@ -11,4 +11,4 @@ All notable changes to this project will be documented in this file, per [the Ke
 
 ### Removes
 
-[Unreleased]: https://github.com/Rahmon/wp-docker/compare/master...develop
+[Unreleased]: https://github.com/Rahmon/wpdocker/compare/master...develop

CONTRIBUTING.md

@@ -10,11 +10,11 @@ Contributing isn't just writing code - it's anything that improves the project.
 
 ### Reporting bugs
 
-If you're running into an issue, please take a look through [existing issues](https://github.com/Rahmon/wp-docker/issues) and [open a new one](https://github.com/Rahmon/wp-docker/issues/new) if needed.  If you're able, include steps to reproduce, environment information, and screenshots/screencasts as relevant.
+If you're running into an issue, please take a look through [existing issues](https://github.com/Rahmon/wpdocker/issues) and [open a new one](https://github.com/Rahmon/wpdocker/issues/new) if needed.  If you're able, include steps to reproduce, environment information, and screenshots/screencasts as relevant.
 
 ### Suggesting enhancements
 
-New features and enhancements are also managed via [issues](https://github.com/Rahmon/wp-docker/issues).
+New features and enhancements are also managed via [issues](https://github.com/Rahmon/wpdocker/issues).
 
 ### Pull requests
 
@@ -33,7 +33,7 @@ The `develop` branch is the development branch which means it contains the next
 1. Readme updates: Make any other readme changes to `README.md` as necessary.
 1. Merge: Make a non-fast-forward merge from your release branch to `develop` (or merge the pull request), then do the same for `develop` into `master` (`git checkout master && git merge --no-ff develop`). `master` contains the stable development version.
 1. Push: Push your master branch to GitHub (e.g. `git push origin master`).
-1. Release: Create a [new release](https://github.com/Rahmon/wp-docker/releases/new), naming the tag and the release with the new version number, and targeting the `master` branch. Paste the changelog from `CHANGELOG.md` into the body of the release and include a link to the closed issues on the [milestone](https://github.com/Rahmon/wp-docker/milestone/#?closed=1).
-1. Close milestone: Edit the [milestone](https://github.com/Rahmon/wp-docker/milestone/#) with release date (in the `Due date (optional)` field) and link to GitHub release (in the `Description` field), then close the milestone.
+1. Release: Create a [new release](https://github.com/Rahmon/wpdocker/releases/new), naming the tag and the release with the new version number, and targeting the `master` branch. Paste the changelog from `CHANGELOG.md` into the body of the release and include a link to the closed issues on the [milestone](https://github.com/Rahmon/wpdocker/milestone/#?closed=1).
+1. Close milestone: Edit the [milestone](https://github.com/Rahmon/wpdocker/milestone/#) with release date (in the `Due date (optional)` field) and link to GitHub release (in the `Description` field), then close the milestone.
 1. Punt incomplete items: If any open issues or PRs which were milestoned for `X.Y.Z` do not make it into the release, update their milestone to `X.Y.Z+1`, `X.Y+1.0`, `X+1.0.0` or `Future Release`.
 1. Update [NPM](https://www.npmjs.com/package/wp-local-docker) with the latest version.

README.md

@@ -2,7 +2,7 @@
 
 > WP Docker is an easy to use Docker based local development environment for WordPress development that works on Mac, Windows, and Linux.
 
-[![Release Version](https://img.shields.io/github/release/Rahmon/wp-docker.svg)](https://github.com/Rahmon/wp-docker/releases/latest) [![MIT License](https://img.shields.io/github/license/Rahmon/wp-docker.svg)](https://github.com/Rahmon/wp-docker/blob/master/LICENSE)
+[![Release Version](https://img.shields.io/github/release/Rahmon/wpdocker.svg)](https://github.com/Rahmon/wpdocker/releases/latest) [![MIT License](https://img.shields.io/github/license/Rahmon/wpdocker.svg)](https://github.com/Rahmon/wpdocker/blob/master/LICENSE)
 
 > **Note**<br>
 > This is a fork of [10updocker](https://github.com/10up/wp-local-docker-v2).
@@ -195,7 +195,7 @@ Getting WP Docker up and running on your system involves a few simple steps. Sta
 Next, you can install WP Docker as a global npm package. Run the following command in your terminal:
 
 ```bash
-npm install -g wp-docker
+npm install -g @wpdocker/wpdocker
 ```
 
 To confirm that WP Docker has been installed successfully, you can check its version. Simply type:
@@ -221,7 +221,7 @@ Then, follow the prompts to customise your settings.
 Keeping WP Docker up-to-date is important. To update it, you can run the installation command again. NPM will replace your current version with the latest one. Here's the command:
 
 ```bash
-npm install -g wp-docker
+npm install -g @wpdocker/wpdocker
 ```
 
 ---
@@ -592,7 +592,7 @@ Starting from version 4.0.0, WP Docker has switched from the old [WP Snapshots](
 
 #### Configuration
 
-If you haven't used [Snapshots](https://github.com/10up/snapshots) with [WP Docker](https://github.com/Rahmon/wp-docker) yet, you'll first need to configure Snapshots with your AWS credentials. To do so, run the following command:
+If you haven't used [Snapshots](https://github.com/10up/snapshots) with [WP Docker](https://github.com/Rahmon/wpdocker) yet, you'll first need to configure Snapshots with your AWS credentials. To do so, run the following command:
 
 ```
 wpdocker wp snapshots configure <repository>
@@ -638,7 +638,7 @@ Replace `<command>` with any command that Snapshots accepts. The command is pass
 
 Concurrent environments are limited by the available resources of your host machine.
 
-### I am having issues with wp-docker, what are the best troubleshooting techniques?
+### I am having issues with wpdocker, what are the best troubleshooting techniques?
 
 See the [Troubleshooting](#troubleshooting) section.
 
@@ -724,10 +724,10 @@ Facing issues with WP Docker? Here are a few steps you can follow to troubleshoo
 
 1. Update Docker and Node: First, make sure that Docker and Node are up to date.
 
-2. Update wp-docker: Ensure that wp-docker is up to date as well. You can do this by running the following command:
+2. Update wpdocker: Ensure that wpdocker is up to date as well. You can do this by running the following command:
 
 ```
-npm i -g wp-docker
+npm i -g @wpdocker/wpdocker
 ```
 
 3. Restart Docker: Once everything is up to date, it's generally a good idea to restart Docker.
@@ -758,7 +758,7 @@ Remember, troubleshooting is a process of elimination. Try these steps one by on
 
 ### Avoiding conflicts with other local dev environments (Valet, MAMP, etc) on macOS
 
-If you are running something like MAMP or Laravel Valet on your Mac, it is possible you may have port conflicts when attempting to use wp-docker, such as:
+If you are running something like MAMP or Laravel Valet on your Mac, it is possible you may have port conflicts when attempting to use wpdocker, such as:
 
 ```
 Cannot start service mysql: Ports are not available: listen tcp 127.0.0.1:3306: bind: address already in use
@@ -773,7 +773,7 @@ sudo lsof -i -P | grep LISTEN
 sudo lsof -i -P | grep :3306
 ```
 
-If you see a process that is using that port, that process should be stopped before you attempt to start or create any new environments with wp-docker.
+If you see a process that is using that port, that process should be stopped before you attempt to start or create any new environments with wpdocker.
 
 If you installed `mysqld` via Homebrew, you need to stop the process via Homebrew:
 
@@ -811,7 +811,7 @@ If that doesn't resolve the issues, try updating your Docker images using `wpdoc
 
 ## Migrating from 10updocker
 
-If you already have 10updocker installed and working, you can install wpdocker (`npm install -g wp-docker`) and start
+If you already have 10updocker installed and working, you can install wpdocker (`npm install -g @wpdocker/wpdocker`) and start
 using it by typing `wpdocker` instead of `10updocker` e.g. `wpdocker start`. Your settings will remain the same. At this
 point, you just changed the name of the tool.
 

package.json

@@ -1,11 +1,11 @@
 {
-	"name": "wp-docker",
+	"name": "@wpdocker/wpdocker",
 	"version": "1.0.0",
 	"description": "WP Docker",
 	"license": "MIT",
-	"homepage": "https://github.com/Rahmon/wp-docker",
+	"homepage": "https://github.com/Rahmon/wpdocker",
 	"bugs": {
-		"url": "https://github.com/Rahmon/wp-docker/issues"
+		"url": "https://github.com/Rahmon/wpdocker/issues"
 	},
 	"keywords": [
 		"wordpress",
@@ -44,7 +44,7 @@
 	},
 	"repository": {
 		"type": "git",
-		"url": "git+ssh://git@github.com/Rahmon/wp-docker.git"
+		"url": "git+ssh://git@github.com/Rahmon/wpdocker.git"
 	},
 	"engines": {
 		"node": ">=18"

src/command-utils.js

@@ -6,7 +6,7 @@ const chalk = require( 'chalk' );
 
 const envUtils = require( './env-utils' );
 
-exports.checkIfDockerRunning = function() {
+exports.checkIfDockerRunning = function () {
 	let output;
 
 	try {
@@ -22,7 +22,7 @@ exports.checkIfDockerRunning = function() {
 	return true;
 };
 
-exports.checkForUpdates = async function() {
+exports.checkForUpdates = async function () {
 	const pkg = require( path.join( envUtils.rootPath, 'package' ) );
 	let update = null;
 
@@ -33,6 +33,6 @@ exports.checkForUpdates = async function() {
 	}
 
 	if ( update ) {
-		console.warn( chalk.yellow( `WP Docker version ${ update.latest } is now available. Please run \`npm i -g wp-docker\` to update!` ) );
+		console.warn( chalk.yellow( `WP Docker version ${ update.latest } is now available. Please run \`npm i -g @wpdocker/wpdocker\` to update!` ) );
 	}
 };