[PR #4583] [MERGED] chore(cli): drop Node.js `v18` support #4864

New issue

Closed

opened 2026-03-17 02:21:40 +03:00 by kerem · 0 comments

kerem commented

2026-03-17 02:21:40 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/hoppscotch/hoppscotch/pull/4583
Author: @jamesgeorge007
Created: 12/2/2024
Status: ✅ Merged
Merged: 12/2/2024
Merged by: @jamesgeorge007

Base: main ← Head: cli-drop-node-v18-support

📝 Commits (1)

5c5343e chore: drop Node.js v18 support for the CLI

📊 Changes

4 files changed (+129 additions, -74 deletions)

View changed files

📝 packages/hoppscotch-cli/bin/hopp.js (+39 -9)
📝 packages/hoppscotch-cli/package.json (+7 -6)
📝 packages/hoppscotch-cli/tsup.config.ts (+2 -2)
📝 pnpm-lock.yaml (+81 -57)

📄 Description

What's changed

This PR aims to drop Node.js v18 support for the CLI. Also, the user is warned if they are on an unsupported Node.js version.

Context: There were compatibility issues observed from v0.12.0 of the CLI with Node.js v18 and with v0.13.0 introduced the File API as part of the public data structured maintained under hoppscotch-data which gets inlined in the CLI bundle leading to errors while installing.

Ref: #4578, #4580, HFE-680.

Changes

Relevant Node.js version checks are introduced before CLI execution and a warning is displayed when appropriate. The further CLI source bundle is dynamically imported after the above checks preventing errors due to unrecognized APIs in older Node.js versions.
Adds semver as a dev dependency for seamless version checks that are inlined in the CLI bundle.
Bump the CLI version and node version under the engines field as part of package.json.
Formatting updates.

Preview

Notes to reviewers

Please pull the CLI published on the Verdaccio instance and verify the error reporting flows on unsupported Node.js versions and other flows in general.

Also, for Node.js versions before 14, there might be errors with the usage of top-level await, optional chaining, etc, which can be ignored since they have reached EOL.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/hoppscotch/hoppscotch/pull/4583 **Author:** [@jamesgeorge007](https://github.com/jamesgeorge007) **Created:** 12/2/2024 **Status:** ✅ Merged **Merged:** 12/2/2024 **Merged by:** [@jamesgeorge007](https://github.com/jamesgeorge007) **Base:** `main` ← **Head:** `cli-drop-node-v18-support` --- ### 📝 Commits (1) - [`5c5343e`](https://github.com/hoppscotch/hoppscotch/commit/5c5343e5994c26cef8f8ba938515deeb907a46e6) chore: drop Node.js v18 support for the CLI ### 📊 Changes **4 files changed** (+129 additions, -74 deletions) <details> <summary>View changed files</summary> 📝 `packages/hoppscotch-cli/bin/hopp.js` (+39 -9) 📝 `packages/hoppscotch-cli/package.json` (+7 -6) 📝 `packages/hoppscotch-cli/tsup.config.ts` (+2 -2) 📝 `pnpm-lock.yaml` (+81 -57) </details> ### 📄 Description ### What's changed This PR aims to drop Node.js `v18` support for the CLI. Also, the user is warned if they are on an unsupported Node.js version. Context: There were compatibility issues observed from `v0.12.0` of the CLI with Node.js v18 and with `v0.13.0` introduced the `File` API as part of the public data structured maintained under `hoppscotch-data` which gets inlined in the CLI bundle leading to errors while installing. Ref: #4578, #4580, HFE-680. ### Changes - Relevant Node.js version checks are introduced before CLI execution and a warning is displayed when appropriate. The further CLI source bundle is dynamically imported after the above checks preventing errors due to unrecognized APIs in older Node.js versions. - Adds `semver` as a dev dependency for seamless version checks that are inlined in the CLI bundle. - Bump the CLI version and `node` version under the `engines` field as part of `package.json`. - Formatting updates. ### Preview ![image](https://github.com/user-attachments/assets/dd263b73-3f0b-4f53-b252-a969e72cb808) ### Notes to reviewers Please pull the CLI published on the Verdaccio instance and verify the error reporting flows on unsupported Node.js versions and other flows in general. Also, for Node.js versions before `14`, there might be errors with the usage of top-level `await`, optional chaining, etc, which can be ignored since they have reached EOL. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>