Merge pull request #28 from qubyte/ES2022

Updates to include ES2022 variants.

Author: qubyte

.github/workflows/ci.yml

@@ -12,9 +12,9 @@ jobs:
     steps:
     - name: checkout
       uses: actions/checkout@main
-    - name: use node 14
-      uses: actions/setup-node@v2
+    - name: use node 18
+      uses: actions/setup-node@v3
       with:
-        version: 14.x
+        node-version: 18.x
     - run: npm ci
     - run: npm test

ES2022-module.js

@@ -0,0 +1,9 @@
+'use strict';
+
+module.exports = {
+  extends: require('path').join(__dirname, 'ES2022.js'),
+  parserOptions: {
+    ecmaVersion: 2022,
+    sourceType: 'module'
+  }
+};

ES2022.js

@@ -0,0 +1,8 @@
+'use strict';
+
+module.exports = {
+  extends: require('path').join(__dirname, 'ES2021.js'),
+  env: {
+    es2022: true
+  }
+};

README.md

@@ -33,7 +33,7 @@ rules as you like.
 ## ES2015 Node.js project.
 
 As before the environment needs to be specified. Since Node 6+ has good ES2015
-feature coverage, it makes sense to use ES2015 features. A sharable config is
+feature coverage, it makes sense to use ES2015 features. A shareable config is
 provided for ES2015 code:
 
 ```json
@@ -47,7 +47,7 @@ provided for ES2015 code:
 
 Internally this config extends the base qubyte config.
 
-## ES2017, ES2018, ES2019, ES2020, ES2021
+## ES2017, ES2018, ES2019, ES2020, ES2021, ES2022
 
 These are mostly the same as ES2015, but with updated parser configuration and
 globals so that ESLint doesn't fall over around things like object spreading.
@@ -57,7 +57,7 @@ globals so that ESLint doesn't fall over around things like object spreading.
 The variants with `-module` in their names are set up for ES module based
 projects. These are provided because setting `parserOptions` in an extending
 ESLint config wipes out the `parserOptions` it provides rather than merging
-them, and this is easy to forget to handle. to use, for example for ES2021:
+them, and this is easy to forget to handle. To use, for example for ES2021:
 
 ```json
 {