npm hook ls duplicates hook name prefixes

[Dionysusnu]

Hooks for scopes get a double prefix, ie @@scope, when shown with the npm hook ls command. This is due to the response from the web request already including the prefix in the name field, and the following lines of code then locally adding the prefix again, duplicating it.

[ashutoshdhande]

@Dionysusnu can i work on this issue? if yes any extra guidance you would like to provide

[Dionysusnu]

It appears that the hooks feature has been disabled on the server side anyways, so I wouldn't waste time on a low priority thing like this.

[Bruce-Hopkins]

If this has been disabled on the server-side, can't we close the issue?

[ljharb]

@Bruce-Hopkins it could still be used by private registries.

[Dionysusnu]

If this has been disabled on the server-side, can't we close the issue?

To clarify, the hooks can still get created, modified, and all that around it, so the bug still exists.

However, in my testing, the actual hook configured URL was never accessed when the hook should have triggered. That's what I meant by "seemingly disabled on the server side".

[552020]

Since this issue is tagged as 'good first issue' and since people looking for 'good first issues' are looking for good first issues that can be assigned now, maybe it would be appropriate to remove the tag.

[ljharb]

@552020 it still is one. The above comments are just folks who don’t think it’s worth the effort, but nobody from npm has agreed with that.