di-sukharev / di-sukharev/opencommit

[Bug]: crypto package deprecated warning on package install

Open
#421 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
7.5k
Forks
445
Avg merge
18m
Merged PRs (30d)
2

Description

Opencommit Version

3.2.2

Node Version

22.9.0

NPM Version

10.8.3

What OS are you seeing the problem on?

Mac

What happened?

installing open commit with the following command: npm i -g opencommit@latest is returning the following warning:

npm warn deprecated crypto@1.0.1: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in. 
Expected Behavior

should not return the error

Current Behavior

it is returning the error

Possible Solution

use the native crypto package as suggested, eventually with a polyfield

Steps to Reproduce

just install the package with npm i -g opencommit@latest on node 22.9.0

Relevant log output
% npm i -g opencommit@latest
npm warn deprecated crypto@1.0.1: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the warning with npm i -g opencommit@latest on Node 22.9.0, then inspect the package's dependency metadata to find the deprecated crypto dependency. Done means the package installs without that deprecation warning while preserving the required crypto functionality.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
build-system, cli
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.