chore: remove support for Node.js v12

Author: davidmurdoch

.github/workflows/pr.yml

@@ -10,7 +10,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        node: [12.0.0, 12.x, 14.x, 16.x, 18.x]
+        node: [14.0.0, 14.x, 16.x, 18.x]
         os: [windows-2019, ubuntu-18.04, ubuntu-20.04, macos-11]
         exclude:
           # Node v18 does not run on ubuntu-18.04: https://github.com/nodejs/node/issues/42351#issuecomment-1068424442

.github/workflows/push.yml

@@ -10,7 +10,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        node: [12.0.0, 12.x, 14.x, 16.x, 18.x]
+        node: [14.0.0, 14.x, 16.x, 18.x]
         os: [ubuntu-20.04]
 
     runs-on: ${{ matrix.os }}

.nvmrc

@@ -1 +1 @@
-v12.0.0
+v14.0.0

CONTRIBUTING.md

@@ -2,11 +2,11 @@
 
 ## Getting set up
 
-- Use Node.js v12.0.0.
-  - Why v12.0.0? Because this is the first LTS release of Node.js v12 and is the earliest version Ganache supports.
+- Use Node.js v14.0.0.
+  - Why v14.0.0? Because this is the first LTS release of Node.js v14 and is the earliest version Ganache supports.
   - recommendation: use [nvm](https://github.com/nvm-sh/nvm) on Linux and macOS, and [nvm-windows](https://github.com/coreybutler/nvm-windows) on
     Windows, to configure your node version.
-    - On Linux and macOS, if you have `nvm` installed, just run `nvm use` to switch to Node.js v12.0.0.
+    - On Linux and macOS, if you have `nvm` installed, just run `nvm use` to switch to Node.js v14.0.0.
 - `git clone [email protected]:trufflesuite/ganache.git`
 - `cd ganache`
 - `npm install` (use npm v6)
@@ -153,7 +153,7 @@ index 2a2aa9e..57cbf21 100644
 
 These are guidelines, not rules. :-)
 
-- Use Node.js v12.0.0 for most local development.
+- Use Node.js v14.0.0 for most local development.
 - Use `bigint` literals, e.g., `123n`; if the number is externally configurable and/or could exceed
   `Number.MAX_SAFE_INTEGER`.
 - Write tests.

UPGRADE-GUIDE.md

@@ -1,5 +1,13 @@
 # Ganache Upgrade Guide
 
+## ganache v7.0.0 - v7.4.3 to ganache v7.5.0+
+
+Node.js v12 and v13 support have been removed. You must upgrade your version of
+Node to v14 or later.
+
+Kovan support has been removed. If you need Kovan support you must use an older
+version of ganache.
+
 ## ganache-core v2.x.x and ganache-cli v6.x.x to ganache v7.x.x
 
 ### Installing
@@ -89,8 +97,8 @@ depending on how you originally installed ganache-cli or ganache-core._
 #### Allowed transaction signature changes
 
 Previously, Ganache allowed transaction signatures to originate from 3 chains
- ids: `1`, `chainId`, and `networkId`. Ganache now allows only transactions
- signed with its own `chainId`.
+ids: `1`, `chainId`, and `networkId`. Ganache now allows only transactions
+signed with its own `chainId`.
 
 #### `_chainId` and `_chainIdRpc` options removed
 
@@ -113,7 +121,7 @@ and it defaulted to `true`.
 
 Ganache now _disables_ the `vmErrorsOnRPCResponse` functionality by default.
 
-If your code relies on these non-standard errors on transaction failure, you'll 
+If your code relies on these non-standard errors on transaction failure, you'll
 need to _enable_ the `vmErrorsOnRpcResponse` flag to restore this behavior:
 
 ```console
@@ -144,7 +152,7 @@ You may want to remove your old Docker images and containers and then pull
 Ganache from the new location before updating, but this step is not required.
 
 > Note: Before updating you may want to prune your Docker images and containers.
- Read more on [docker pruning](https://docs.docker.com/config/pruning/).
+> Read more on [docker pruning](https://docs.docker.com/config/pruning/).
 
 You can view the list of local Docker containers by running:
 
@@ -183,7 +191,6 @@ or to pull and run it simultaneously:
 $ docker run --port 8545:8545 trufflesuite/ganache:latest
 ```
 
-
 #### Default startup ether is now 1000 instead of 100
 
 We polled 50 developers about Ganache's startup Ether amount. 44% had no
@@ -207,7 +214,7 @@ ganache.provider({
   wallet: {
     defaultBalance: 100
   }
-})
+});
 ```
 
 #### Ganache's provider and server interfaces have changed
@@ -222,8 +229,8 @@ If you were previously programmatically accessing the VM step events by
 traversing Ganache internals you can now access these via a new Event System:
 
 In addition to [EIP-1193's](https://eips.ethereum.org/EIPS/eip-1193) `"message"`
- event and the legacy `"data"` event, Ganache emits 3 additional events:
- `"ganache:vm:tx:before"`, `"ganache:vm:tx:step"`, and `"ganache:vm:tx:after"`.
+event and the legacy `"data"` event, Ganache emits 3 additional events:
+`"ganache:vm:tx:before"`, `"ganache:vm:tx:step"`, and `"ganache:vm:tx:after"`.
 
 These events can be used to observe the lifecycle of any transaction executed
 via `*sendTransaction`, `eth_call`, `debug_traceTransaction`, or `debug_storageRangeAt`.
@@ -286,7 +293,7 @@ likely enable this in the future.
 
 Ganache's old database format is incompatible with this version. We've decided
 to hold off on building migration tools for this. If you will need a migration
-tool (you use the `db` flag or the `db_path` option and are unable to recreate 
+tool (you use the `db` flag or the `db_path` option and are unable to recreate
 your initial DB state) please
 [open an issue](https://github.com/trufflesuite/ganache/issues/new)
 to let us know.
@@ -341,7 +348,7 @@ If you send a transaction with `eth_sendTransaction` and that transaction doesn'
 
 ```typescript
 // send a "legacy" transaction
-const hash = await provider.request("eth_sendTransaction", [{ from }]); 
+const hash = await provider.request("eth_sendTransaction", [{ from }]);
 const tx = await provider.request("eth_getTransactionByHash", [hash]);
 // The returned `type` field indicates it was updated to a type 2 transaction
 assert.strictEqual(tx.type, "0x2");
@@ -433,17 +440,17 @@ sending account to cover the maximum cost.
 - `logs` subscription events are emitted before `newHeads` events
 - the default `callGasLimit` has changed from `Number.MAX_SAFE_INTEGER` ($2^{53} - 1$) to `50_000_000`.
 
-
-
-[^1]: yarn and pnpm don't support dependency lock files, like npm's npm-shrinkwrap.json,
-which permits supply-chain attacks through automatic transitive dependency
-updates, like the [left-pad attack](https://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm.html) and mostly recently the
-[colors and faker attack](https://security.snyk.io/vuln/SNYK-JS-COLORS-2331906).
-
-[^2]: `eth_call` can't always perfectly reproduce the state that the original
-transaction was run in if other transactions run before it in a block. This is
-very rare in testing scenarios, but should be something you are aware of. We'll
-be addressing this shortcoming in a future EIP and release by extending eth_call
-with an option to run the transaction at a certain _index_ in the specified
-block (you likely won't ever see this option enabled on public nodes, like
-Infura, as it can be a very CPU-intensive process).
+[^1]:
+    yarn and pnpm don't support dependency lock files, like npm's npm-shrinkwrap.json,
+    which permits supply-chain attacks through automatic transitive dependency
+    updates, like the [left-pad attack](https://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm.html) and mostly recently the
+    [colors and faker attack](https://security.snyk.io/vuln/SNYK-JS-COLORS-2331906).
+
+[^2]:
+    `eth_call` can't always perfectly reproduce the state that the original
+    transaction was run in if other transactions run before it in a block. This is
+    very rare in testing scenarios, but should be something you are aware of. We'll
+    be addressing this shortcoming in a future EIP and release by extending eth*call
+    with an option to run the transaction at a certain \_index* in the specified
+    block (you likely won't ever see this option enabled on public nodes, like
+    Infura, as it can be a very CPU-intensive process).

package.json

@@ -3,7 +3,7 @@
   "author": "David Murdoch <[email protected]> (https://davidmurdoch.com)",
   "private": true,
   "engines": {
-    "node": ">=12.0.0",
+    "node": ">=14.0.0",
     "npm": ">=6.12.0"
   },
   "scripts": {

src/packages/ganache/README.md

@@ -47,7 +47,7 @@ Ganache can be used from the [command line](#command-line-use), [programmaticall
 
 ### Command line use
 
-You must first install [Node.js](https://nodejs.org/) >= v12.0.0 and npm >= 6.12.0.
+You must first install [Node.js](https://nodejs.org/) >= v14.0.0 and npm >= 6.12.0.
 
 To install Ganache globally, run: