tiny-care-terminal icon indicating copy to clipboard operation
tiny-care-terminal copied to clipboard

Compatibility and Deprecation Issues with tiny-care-terminal on Node.js v20.15.0

Open Bklyn97 opened this issue 7 months ago • 0 comments

Description

Attempting to install [email protected] globally on Windows with Node.js v20.15.0 results in multiple compatibility issues and deprecation warnings, leading to a failed installation.

Environment

  • Node Version: 20.15.0 (Output from node --version)
  • tiny-care-terminal Version: 1.8.0 (Output from npm info tiny-care-terminal | grep version:)
  • Operating System: Windows 10 Pro 64-bit
  • Powershell 7.4.3

Expected Behavior

The package should install without issues and function as expected without warnings about deprecated dependencies or node version incompatibilities.

Actual Behavior

The installation triggers multiple errors:

  1. Node Version Unsupported: Requires Node >=6.10.3 <10, but running v20.15.0.
  2. Deprecated Modules: Several dependencies are outdated, including request, uuid below version 7, and glob below version 9.
  3. Permission Errors: Errors related to permission issues (EPERM) during cleanup stages.
  4. Build Failures: node-gyp build failures due to incompatibilities and possibly incorrect setup or missing distutils in Python.

Steps to Reproduce

  1. Open a terminal window.
  2. Execute npm install -g tiny-care-terminal.
  3. Review the terminal output for errors and warnings listed above.

Possible Solutions

  • Node.js Compatibility: Update the package to support modern Node.js versions.
  • Dependencies: Upgrade deprecated dependencies to their supported versions.
  • Installation Guide: Improve documentation to handle installation dependencies more clearly, especially regarding node-gyp and Python setup.

Additional Context

Below is a log of the error message

Suggested Next Steps

  • Evaluating the feasibility of updating the package or potentially forking it to maintain compatibility with newer development environments would be beneficial.

Thank you for addressing these issues and for your support! Any guidance would be greatly appreciated.


Here's a cleaned-up version of the npm installation log, without identifiable information while retaining essential details for debugging:

PS> npm install -g tiny-care-terminal npm warn EBADENGINE Unsupported engine { npm warn EBADENGINE package: '[email protected]', npm warn EBADENGINE required: { node: '>=6.10.3 <10' }, npm warn EBADENGINE current: { node: 'v20.15.0', npm: '10.8.0' } npm warn EBADENGINE } npm warn deprecated [email protected]: This module is not supported, and leaks memory. npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm warn deprecated [email protected]: this library is no longer supported npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported npm warn deprecated [email protected]: Please upgrade to version 7 or higher. npm warn deprecated [email protected]: request has been deprecated. npm warn cleanup Failed to remove some directories [ npm warn cleanup [ npm warn cleanup '[npm directory path]', npm warn cleanup [Error: EPERM: operation not permitted, rmdir '[path]'] npm warn cleanup ], npm warn cleanup [ npm warn cleanup '[npm directory path]', npm warn cleanup [Error: EPERM: operation not permitted, rmdir '[path]'] npm warn cleanup ] npm warn cleanup ] npm error code 1 npm error command failed npm error command [System command path] /d /s /c node-gyp rebuild npm error gyp info it worked if it ends with ok npm error gyp info using node-gyp@[version] npm error gyp info using node@[version] | win32 | x64 npm error gyp info find Python using Python version [version] found at "[Python installation path]" npm error gyp info find VS using VS2019 ([version]) found at: npm error gyp info find VS "[VS installation path]" npm error gyp info find VS run with --verbose for detailed information npm error gyp info spawn [Python installation path] npm error gyp info spawn args [ npm error gyp info spawn args '[file paths and parameters]' npm error gyp info spawn args ] npm error Traceback (most recent call last): npm error File "[node-gyp path]\gyp\gyp_main.py", line 42, in npm error import gyp npm error File "[node-gyp path]\gyp\pylib\gyp_init_.py", line 9, in npm error import gyp.input npm error File "[node-gyp path]\gyp\pylib\gyp\input.py", line 19, in npm error from distutils.version import StrictVersion npm error ModuleNotFoundError: No module named 'distutils' npm error gyp ERR! configure error npm error gyp ERR! stack Error: gyp failed with exit code: 1 npm error gyp ERR! stack at ChildProcess.onCpExit ([node-gyp path]\lib\configure.js:259:16) npm error gyp ERR! stack at ChildProcess.emit (node:events:519:28) npm error gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:294:12) npm error gyp ERR! System Windows_NT [OS version] npm error gyp ERR! command "[node path]" "[node-gyp path]\bin\node-gyp.js" "rebuild" npm error gyp ERR! cwd [current working directory] npm error gyp ERR! node -v [node version] npm error gyp ERR! node-gyp -v [node-gyp version] npm error gyp ERR! not ok npm error A complete log of this run can be found in: [log file path] PS>

Bklyn97 avatar Jul 13 '24 02:07 Bklyn97