Modernize stack esm vitest upgrade dependencies

.github/workflows/pull_requests.yml

@@ -24,7 +24,7 @@ jobs:
     runs-on: ubuntu-latest
     timeout-minutes: 15
     container:
-      image: mcr.microsoft.com/playwright:v1.53.1-jammy
+      image: mcr.microsoft.com/playwright:v1.57.0-jammy
     env:
       MPKIT_EMAIL: ${{ secrets.MPKIT_EMAIL }}
       MPKIT_TOKEN: ${{ secrets.MPKIT_TOKEN }}

.github/workflows/tests.yaml

@@ -8,13 +8,14 @@ on:
 
 jobs:
   test:
-    runs-on: ubuntu-latest
+    runs-on: ${{ matrix.os }}
     timeout-minutes: 15
 
     strategy:
       max-parallel: 1
       matrix:
-        version: ['18', '20', '20.11']
+        os: [windows-latest, ubuntu-latest]
+        version: ['22', '24']
 
     steps:
       - name: Checkout repository
@@ -31,7 +32,7 @@ jobs:
           MPKIT_URL: ${{ secrets.TEST_MPKIT_URL }}
           POS_PORTAL_PASSWORD:  ${{secrets.POS_PORTAL_PASSWORD}}
           CI: true
-        shell: sh
+        shell: bash
         run: |
           npm ci
           npm test

.npmrc

@@ -1,2 +1 @@
 scope=@platformos
-save=false

CHANGELOG.md

@@ -1,5 +1,37 @@
 # Changelog
 
+## Unreleased
+
+
+## 6.0.0
+
+* Feature: `pos-cli exec liquid` command to execute Liquid code directly on an instance (supports `-f` flag to load from file, requires confirmation on production)
+* Feature: `pos-cli exec graphql` command to execute GraphQL queries directly on an instance (supports `-f` flag to load from file, requires confirmation on production)
+* Feature: `pos-cli test run` command to run tests using the tests module
+
+### Major Dependency Upgrades
+
+We've completed a comprehensive modernization of the CLI including:
+
+**Node.js Version Requirement**: Now requires Node.js 20 or higher (up from Node.js 18)
+
+**Breaking Changes** that may require action from users:
+
+1. **Yeoman generators**: If you have custom generators using `yeoman-generator`, they need to be rewritten for the v7.x update:
+   - No kebab-case in option names (e.g., `skip-install` → `skipInstall`)
+   - `composeWith()` is now async (use `await`)
+   - The `install()` action has been removed; use `addDependencies()` instead
+   - See [yeoman-generator v5 to v7 migration guide](https://yeoman.github.io/generator/v5-to-v7-migration/)
+
+2. **Express v5 route syntax**: Routes using wildcards have changed from `/*` to `/*splat` format. This is handled automatically, but if you have custom Express middleware in your project, you may need to update route patterns.
+
+**Package Upgrades**: All major dependencies have been updated to their latest stable versions including:
+- chalk v5.6, chokidar v5.0, express v5.2, ora v9.0, open v11.0
+- inquirer v13.2, mime v4.1, multer v2.0, yeoman-environment v5.1, yeoman-generator v7.5
+- And many other dependency updates for security and stability
+
+**Test Framework Migration**: Migrated from Jest to Vitest to better support ESM
+
 ## 5.5.0
 
 * Feature: (GUI) Ability to add, edit and remove users

CLAUDE.md

@@ -90,14 +90,14 @@ pos-cli/
 Example:
 ```javascript
 // bin/pos-cli-deploy.js
-const fetchAuthData = require('../lib/settings').fetchSettings;
-const deployStrategy = require('../lib/deploy/strategy');
+import { fetchSettings } from '../lib/settings';
+import deployStrategy from '../lib/deploy/strategy.js';
 
 program
   .argument('[environment]', 'name of environment')
   .option('-p --partial-deploy', 'Partial deployment')
   .action(async (environment, params) => {
-    const authData = fetchAuthData(environment);
+    const authData = fetchSettings(environment);
     deployStrategy.run({ strategy: 'directAssetsUpload', opts: { ... } });
   });
 ```
@@ -139,11 +139,17 @@ Two deployment strategies:
 
 Strategy selection:
 ```javascript
+import defaultStrategy from './defaultStrategy.js';
+import directAssetsUploadStrategy from './directAssetsUploadStrategy.js';
+
 const strategies = {
-  default: require('./defaultStrategy'),
-  directAssetsUpload: require('./directAssetsUploadStrategy'),
+  default: defaultStrategy,
+  directAssetsUpload: directAssetsUploadStrategy,
 };
-module.exports = { run: ({ strategy, opts }) => strategies[strategy](opts) };
+
+const run = ({ strategy, opts }) => strategies[strategy](opts);
+
+export { run };
 ```
 
 #### 3. File Watching Pattern - Sync Mode
@@ -354,6 +360,8 @@ GUI apps are pre-built (in dist/ or build/ directories). To modify:
 - **CDN** - Asset delivery and verification
 
 ## Node.js Version
-- **Minimum**: Node.js 18
-- **Tested on**: 18, 20, 20.11
+
+- **Minimum**: Node.js 22
+- **Recommended**: Node.js 22+
+- **Tested on**: 22, 24
 - Check enforced by `scripts/check-node-version.js` postinstall hook

README.md

@@ -8,7 +8,7 @@ Run all commands from the project root directory, one level above the `app` or `
 
 ### Requirements
 
-`pos-cli` requires Node.js version 18 or higher to function correctly. [See instructions for installing Node.js on your platform](https://nodejs.org/en/download/).
+`pos-cli` requires Node.js version 22 or higher to function correctly. [See instructions for installing Node.js on your platform](https://nodejs.org/en/download/).
 
 ## Installation and Update
 
@@ -444,6 +444,60 @@ If you need guidance or additional information about how to use a specific gener
 
     pos-cli generate modules/core/generators/command --generator-help
 
+### Executing Code
+
+#### Execute Liquid
+
+Execute Liquid code directly on your instance:
+
+    pos-cli exec liquid [environment] [code]
+
+Example:
+
+    pos-cli exec liquid staging "{{ 'hello' | upcase }}"
+
+You can also execute Liquid code from a file using the `-f` flag:
+
+    pos-cli exec liquid staging -f path/to/script.liquid
+
+#### Execute GraphQL
+
+Execute GraphQL queries directly on your instance:
+
+    pos-cli exec graphql [environment] [query]
+
+Example:
+
+    pos-cli exec graphql staging "{ users(per_page: 5) { results { id email } } }"
+
+You can also execute GraphQL from a file using the `-f` flag:
+
+    pos-cli exec graphql staging -f path/to/query.graphql
+
+**Note:** When executing on production environments (environment name contains "prod" or "production"), you will be prompted for confirmation before execution.
+
+### Running Tests
+
+To run tests on your instance, you need to have the [tests module](https://github.com/Platform-OS/pos-module-tests) installed.
+
+#### Run All Tests
+
+    pos-cli test run [environment]
+
+Example:
+
+    pos-cli test run staging
+
+This command runs all tests and streams the results in real-time, showing individual test outcomes and a summary at the end.
+
+#### Run a Single Test
+
+    pos-cli test run [environment] [test-name]
+
+Example:
+
+    pos-cli test run staging my_test
+
 ## Development
 
 The `pos-cli gui serve` command uses a distinct build process for the GraphiQL interface located in the `gui/editor/graphql` directory.