commit all work waiting for answers

kmurphypolygon · kmurphypolygon · commit 838fbe00fddf · 2024-02-22T11:32:09.000+01:00
diff --git a/docs/tools/dApp-development/launchpad/commands.md b/docs/tools/dApp-development/launchpad/commands.md
@@ -0,0 +1,114 @@
+## `init`
+
+Initializes a new project in a new directory which has the same name as the project. If a project name is not mentioned, a random one is chosen.
+
+```sh
+dapp-launchpad init [PROJECT-NAME]
+```
+
+### Options
+
+|         Option        |     Description                        |
+|:---------------------:|----------------------------------------|
+| -t, --template [NAME] | Name of the scaffold template to use; default: "javascript". To get list of available templates, run list scaffold-templates. (default: "javascript") |
+| -h, --help            | display help for command               |
+
+### Help
+
+```sh
+dapp-launchpad init -h
+```
+
+## `dev`
+
+Starts a local dev environment; a local blockchain (Hardhat) and a local front end (Next.js) server.
+
+```sh
+dapp-launchpad dev [options]
+```
+
+The `dev` command starts 
+
+### Options
+
+| Option                               | Description                                                                                                                                                                                                    |
+|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| -n, --fork-network-name [NAME]       | Name of the network to fork; optional. By default, it starts a new chain from genesis block. (choices: "ethereum", "goerli", "polygonPos", "polygonMumbai", "polygonZkevm", "polygonZkevmTestnet")             |
+| -b, --fork-block-num [number]        | Block number to fork at. By default, it's the latest block.                                                                                                                                                    |
+| -r, --reset-on-change                | Resets the entire local blockchain when any code is changed; for forked mode, it resets back to forked block number; NOT DEFAULT.                                                                              |
+| --only-smart-contracts               | Deploys only smart contracts (having started local test chain) and updates Smart contract configs for frontend; does not start frontend dev environment.                                                       |
+| --only-frontend                      | Deploys only frontend (having started local server); does not start local blockchain. Smart contracts data is read from pre-existing configs. To generate these manually, use generate smart-contracts-config. |
+| -e, --enable-explorer                | Sets up a chain explorer for the local test blockchain started; NOT DEFAULT; sign up at https://app.tryethernal.com/.                                                                                          |
+| --ethernal-login-email [EMAIL]       | Ethernal login email; needed only if --explorer is enabled. This overrides env variable ETHERNAL_EMAIL if present.                                                                                             |
+| --ethernal-login-password [PASSWORD] | Ethernal login password; needed only if --explorer is enabled. This overrides env variable ETHERNAL_PASSWORD if present.                                                                                       |
+| --ethernal-workspace [WORKSPACE]     | Ethernal workspace name; needed only if --explorer is enabled. This overrides env variable ETHERNAL_WORKSPACE if present.                                                                                      |
+| -h, --help                           | Display help for command                                                                                                                                                                                       |
+
+### Help
+
+```sh
+dapp-launchpad dev -h
+```
+
+## `deploy`
+
+The deploy command deploys the smart contracts and frontend app to production.
+
+```sh
+dapp-launchpad deploy -n CHAIN_NAME
+```
+
+### Options
+
+|        Option         |        Description         |
+|:----------------------:|:-------------------------------------------------------|
+| -n, --network-name     | Name of the network to deploy smart contracts to. (choices: "ethereum", "goerli", "polygonPos", "polygonMumbai", "polygonZkevm", "polygonZkevmTestnet")               |
+| --only-smart-contracts | Deploys only smart contracts and updates Smart contracts config for frontend.                                                                                         |
+| --only-frontend        | Deploys only frontend; smart contracts data is read from Smart contracts config which must pre-exist. To generate these manually, use generate smart-contracts-config |
+| -h, --help             | Display help for command                                                                                                                                              |
+
+### Help
+
+```sh
+dapp-launchpad deploy -h
+```
+
+## `list`
+
+List options.
+
+```sh
+dapp-launchpad list <WHAT TO LIST>
+```
+
+### `scaffold-templates`
+
+List the available scaffold template languages.
+
+```sh
+dapp-launchpad list scaffold-templates
+```
+
+## `generate`
+
+Generate the specified.
+
+```sh
+dapp-launchpad generate <WHAT TO GENERATE>
+```
+
+### `smart-contracts-config`
+
+Generate the smart contract configuration.
+
+```sh
+dapp-launchpad generate smart-contracts-config
+```
+
+### Options
+
+|          Option         |                         Description      |
+|:-----------------------:|:-----------------------------------------|
+| -e, --environment <ENV> | Environment where this config would be used (choices: "development", "production", default: "development")                                        |
+| -n, --network-name      | Name of the network to generate config for. (choices: "ethereum", "goerli", "polygonPos", "polygonMumbai", "polygonZkevm", "polygonZkevmTestnet") |
+| -h, --help              | Display help for command                  |
diff --git a/docs/tools/dApp-development/launchpad/common-pitfalls.md b/docs/tools/dApp-development/launchpad/common-pitfalls.md
@@ -0,0 +1,13 @@
+## MetaMask transactions fail with a nonce error in dev environment 
+
+Every time the dev environment starts, a new local test chain is started. Metamask maintains a cache of "latest block number" and "account transaction nonce". Since every run of `dev` creates a new chain, it never matches with this cache.
+
+To know how to clear the cache, [read this](https://support.metamask.io/hc/en-us/articles/360015488891-How-to-clear-your-account-activity-reset-account).
+
+## MetaMask transactions fail with a nonce error when using the **reset on change** option in dev environment
+
+The reset on change option resets the blockchain on every code change. 
+
+MetaMask maintains a cache of *latest block number* and *account transaction nonce*. After resetting the chain, the latest block number and account transaction nonce should go back to the initial state as well, but MetaMask does not update this cache on its own.
+
+To clear the cache, follow the [MetaMask documentation](https://support.metamask.io/hc/en-us/articles/360015488891-How-to-clear-your-account-activity-reset-account).
diff --git a/docs/tools/dApp-development/launchpad/contributiing.md b/docs/tools/dApp-development/launchpad/contributiing.md
@@ -0,0 +1,42 @@
+## Build from source
+
+To build from source, clone the dApp Launchpad repository.
+
+```sh
+git clone https://github.com/0xPolygon/dapp-launchpad.git
+cd dapp-launchpad
+```
+
+Then build the CLI tool.
+
+```sh
+npm run build
+```
+
+This generates `cli.js` inside the `bin` directory, which can then be installed globally with:
+
+```sh
+npm run install-global
+```
+
+Now `dapp-launchpad` is available as a global command.
+
+## Develop on local
+
+To modify this tool, start a local dev environment by running:
+
+```sh
+npm run dev
+```
+
+This running process watches the source files, bundles up the CLI app on every change, and installs it globally.
+
+This means that the app is continuously updating with changes to the code.
+
+## Report a bugs/request a feature
+
+Create an issue below on the repo:
+
+https://github.com/0xPolygon/dapp-launchpad/issues
+
+Please give as much detail about your issue or request as possible.
diff --git a/docs/tools/dApp-development/launchpad/frontend.md b/docs/tools/dApp-development/launchpad/frontend.md
@@ -6,7 +6,7 @@ To get started, modify the component file at `./frontend/src/pages/index`.
 
 !!! info
     If you're new to Next.js but know React.js, getting used to Next.js is trivial. 
-    To learn more about Next.js, [read their docs](https://nextjs.org/docs).
+    To learn more about Next.js, [read the Next.js docs](https://nextjs.org/docs).
 
 ## Environment variables
 
diff --git a/docs/tools/dApp-development/launchpad/intro.md b/docs/tools/dApp-development/launchpad/intro.md
@@ -1,8 +1,17 @@
 dApp Launchpad is an automated CLI tool for initializing, creating, and deploying a fully-integrated web3 dApp project.
 
+## Overview
+
 dApp projects are divided into two parts:
 
 - [Frontend](frontend.md): The frontend runs on Next.js. 
 - [Smart contracts](smart-contracts.md): The smart contracts use a Hardhat environment.
 
-The tool automates basic activity such as auto-updating contract artifacts, (re)deploying contracts on code changes, and Hot Module Replacement (HMR) for frontend code changes, and more.
+The tool automates basic activity such as auto-updating contract artifacts, (re)deploying contracts on code changes, and Hot Module Replacement (HMR) for frontend code changes, and more.
+
+## Repo
+
+Find the code on the following git repo: https://github.com/0xPolygon/dapp-launchpad
+
+!!! warning
+    Please note the docs in the README are possibly not up-to-date.
diff --git a/docs/tools/dApp-development/launchpad/quickstart.md b/docs/tools/dApp-development/launchpad/quickstart.md
@@ -2,7 +2,7 @@
 
 - [Node](https://nodejs.org/en/download) version 18.x.x is recommended.
 - Anything above Node version 16.14.x is supported.
-- We recommend [https://github.com/nvm-sh/nvm] for managing Node installations.
+- We recommend [https://github.com/nvm-sh/nvm](https://github.com/nvm-sh/nvm) for managing Node installations.
 
 ## Install the app
 
@@ -36,7 +36,7 @@ dapp-launchpad list scaffold-templates
 
 ## Set up environment variables
 
-There are mandatory environment variables in both the frontend and smart contract directories. 
+There are mandatory environment variables in both the `frontend` and `smart-contracts` directories. 
 
 1. `cd` into your project directory.
 
@@ -81,11 +81,11 @@ There are mandatory environment variables in both the frontend and smart contrac
 
     You will see the local test blockchain running with deployed contracts and some pre-funded wallets you can use.
 
-    [Local test environment running](../../../img/tools/launchpad/running-example.png)
+    ![Local test environment running](../../../img/tools/launchpad/running-example.png)
 
 2. Open [http://localhost:3000](http://localhost:3000) in a browser.
 
-    [Web application running](../../../img/tools/launchpad/dev-startup.png)
+    ![Web application running](../../../img/tools/launchpad/dev-startup.png)
 
 You now have a fully integrated dev environment including a local dev blockchain and a local frontend dev server. Any changes to the code automatically updates both the frontend and the smart contracts. No manual reload is necessary.
 
@@ -97,13 +97,22 @@ You can start developing by forking an existing chain. To see the available opti
 dapp-launchpad dev -h
 ```
 
+The chain name options are in this section of the help output:
+
+```sh
+-n, --fork-network-name [NAME]        Name of the network to fork; optional. 
+                                        By default, it starts a new
+                                        chain from genesis block. (choices: "ethereum", "goerli",
+                                        "polygonPos", "polygonMumbai", "polygonZkevm", "polygonZkevmTestnet")
+```
+
 To fork Polygon zkEVM, for example, run the following command:
 
 ```sh
 dapp-launchpad dev -n polygonZkevm
 ```
 
-To fork at a particular block number run the command with the following optional flag:
+To fork at a particular block number run the command including the optional flag `-b`:
 
 ```sh
 dapp-launchpad dev -n polygonZkevm -b [BLOCK_NUMBER_TO_FORK_AT]
@@ -135,10 +144,10 @@ dapp-launchpad deploy -n CHAIN_NAME --only-frontend
 ```
 
 !!! important
-    The frontend deployment requires that smart contracts to have been deployed before, so if you are only deploying the frontend, make sure that you:
+    The frontend deployment requires that smart contracts to have already been deployed, so if you are only deploying the frontend, make sure that you:
 
     1. Have already run the smart contracts deploy command successfully.
-    2. OR, run the following wizard:
+    2. If not, run the following wizard command:
     
             `generate smart-contracts-config -e production -n CHAIN_NAME`
 
diff --git a/docs/tools/dApp-development/launchpad/smart-contracts.md b/docs/tools/dApp-development/launchpad/smart-contracts.md
@@ -6,9 +6,9 @@ Make sure you have followed the [steps in the quickstart](quickstart.md#set-up-e
 
 The smart contracts run on a [Hardhat](https://hardhat.org/) environment. They are written in [Solidity](https://docs.soliditylang.org/) and reside in the `smart-contracts` directory.
 
-Tests are written in JS/TS, and are in the `tests` directory. An example test is available.
+Tests are written in JavaScript and TypeScript, and are in the `tests` directory. An example test is available.
 
-Scripts are also written in JS/TS, and reside in the `scripts` directory. Some mandatory scripts are already there to get started with.
+Scripts are also written in JavaScript and TypeScript, and reside in the `scripts` directory. Some mandatory scripts are already there to get started with.
 
 ## Deploying on local test chain
 
diff --git a/mkdocs.yml b/mkdocs.yml
@@ -429,6 +429,8 @@ nav:
               - Frontend: tools/dApp-development/launchpad/frontend.md
               - Smart contracts: tools/dApp-development/launchpad/smart-contracts.md
               - Commands: tools/dApp-development/launchpad/commands.md
+              - Contributing: tools/dApp-development/launchpad/contributing.md
+              - Common pitfalls: tools/dApp-development/launchpad/common-pitfalls.md
           - Smart contract development on PoS:
               - Alchemy: tools/dApp-development/pos/alchemy.md
               - ChainIDE: tools/dApp-development/pos/chainide.md
