Node Version Conflict Installing V1

Summary

Upgrading from old v0.9 version by running ghost install --v1 does not work.

Steps to Reproduce

1. nvm use 14
2. npm install -g ghost-cli@latest
3. mkdir ghostv1; cd ghostv1
4. ghost install --v1

Run into Ghost v1.26.2 is not compatible with the current Node version. Your node version is 14.19.3, but Ghost v1.26.2 requires ^8.9.0 || ^10.13.0

I then tried running node v10

1. nvm use 10
2. npm install -g ghost-cli@latest
3. ghost install --v1

Run into Error: yargs parser supports a minimum Node.js version of 12.

I expect to be able to install v1 somehow with the latest ghost-cli.

Log file

Love open source? We’re hiring Node.js Engineers to work on Ghost full-time.
https://careers.ghost.org/product-engineer-node-js



✔ Checking system Node.js version - found v14.19.3
✔ Checking logged in user
✔ Checking current folder permissions
✔ Checking system compatibility
✔ Checking for a MySQL installation
✔ Checking memory availability
✔ Checking free space
✔ Checking for latest Ghost version
✔ Setting up install directory
✖ Downloading and installing Ghost v1.26.2
A SystemError occurred.

Message: Ghost v1.26.2 is not compatible with the current Node version. Your node version is 14.19.3, but Ghost v1.26.2 requires ^8.9.0 || ^10.13.0

Debug Information:
    OS: Ubuntu, v16.04.6 LTS
    Node Version: v14.19.3
    Ghost-CLI Version: 1.21.0
    Environment: production
    Command: 'ghost install --v1'

Try running ghost doctor to check your system for known issues.

/home/---/.nvm/versions/node/v10.24.1/lib/node_modules/ghost-cli/node_modules/yargs/node_modules/yargs-parser/build/index.cjs:1013
        throw Error(`yargs parser supports a minimum Node.js version of ${minNodeVersion}. Read our version support policy: https://github.com/yargs/yargs-parser#supported-nodejs-versions`);
        ^

Error: yargs parser supports a minimum Node.js version of 12. Read our version support policy: https://github.com/yargs/yargs-parser#supported-nodejs-versions
    at Object.<anonymous> (/home/---/.nvm/versions/node/v10.24.1/lib/node_modules/ghost-cli/node_modules/yargs/node_modules/yargs-parser/build/index.cjs:1013:15)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/home/---/.nvm/versions/node/v10.24.1/lib/node_modules/ghost-cli/node_modules/yargs/build/index.cjs:1:59793)
    at Module._compile (internal/modules/cjs/loader.js:778:30)

Technical details

This is automatically output by Ghost-CLI if an error occurs, please copy & paste:

• OS: Ubuntu, v16.04.6 LTS
• Node Version: v14.19.3/v10.24.1
• Ghost-CLI Version: 1.21.0
• Environment: production
• Command: ghost install --v1

Bug submission checklist

Please fill out this checklist to acknowledge that you followed the requirements to submit a bug report.

• [ x] Tried to find help in the forum & docs
• [ x] Checked for existing issues
• [ x] Attached log file
• [ x] Provided technical details incl. operating system

[al3x-huang]

I understand the frustration, but unfortunately, this isn’t feasible as it would force Ghost CLI to support node versions that are no longer supported.

Hmm, I guess it’s rather odd to still have a feature like ghost install --v1 present in the latest ghost-cli package if it doesn’t work. Maybe it could be replaced with a deprecation warning message when invoked pointing to an earlier version like ghost-cli@1.10 so users can still upgrade to v1 which is prerequisite to upgrading to latest versions.

At the very least, I think some notes should be made on: https://ghost.org/docs/faq/update-0x/ https://ghost.org/docs/reinstall/

Since both of these documentations cite ghost-cli’s use case for upgrading 0.x to newer versions.

[github-actions[bot]]

Our bot has automatically marked this issue as stale because there has not been any activity here in some time. The issue will be closed soon if there are no further updates, however we ask that you do not post comments to keep the issue open if you are not actively working on a PR. We keep the issue list minimal so we can keep focus on the most pressing issues. Closed issues can always be reopened if a new contributor is found. Thank you for understanding 🙂