Can't generate a new key using ipfs-core

[0xtekgrinder]

• Version:

json { version: '0.17.0', commit: '', repo: '12', system: 'amd64/linux', golang: 'go1.19.1', 'ipfs-http-client': '1.0.0' }

• Platform:

Linux darkside 6.0.12-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Dec 8 17:15:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

• Subsystem:

ipfs-http-client

Severity:

Medium

Description:

• I tried to generate a new key by using ipfs-http-client
• It generate a error HTTPError: unrecognized key type: Ed25519
• It should had generate a new key that I could use with IPNS in ed25519
• I think it happens because the keytype is Ed25519 and not ed25519 (same for RSA instead of rsa)

Steps to reproduce the error:

• Create a configuration of ipfs-http-client
• Generate a new key

import dotenv from 'dotenv';
import { create } from 'ipfs-http-client';
dotenv.config();

const ipfs = create({
    url: process.env.IPFS_API,
})

await ipfs.key.gen("KEY");

[welcome]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

[RangerMauve]

Getting same error when talking to kubo via [email protected] and js-ipfs-http-client@60

[RangerMauve]

I can submit a PR

[whizzzkid]

js-ipfs is being deprecated in favor of Helia. You can follow the migration plan here #4336 and read the migration guide.

Please feel to reopen with any comments before 2023-06-05. We will do a final pass on reopened issues afterward (see #4336).

This issue might be resolved or planned in Helia, if not, please let us know!