Skip to content

[BUG] npm fund <package> errors when "funding" is a string #498

Closed
@panva

Description

@panva

What / Why

While #472 has fixed the npm fund command not showing packages where "funding" is a string, the npm fund <package-name> command doesn't work for these.

In the screenshot below glob got opened, the other one didn't.

Screenshot 2019-11-19 10 58 59

Expected Behavior

npm fund <package> works regardless of the funding property being a shorthand string or an object.

Metadata

Metadata

Assignees

Labels

Bugthing that needs fixingsemver:patchsemver patch level for changes

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions