8000 NPM-friendly `package.json`s · Issue #18 · coder/backstage-plugins · GitHub
[go: up one dir, main page]

Skip to content
NPM-friendly package.jsons #18
Closed as not planned
Closed as not planned
@bpmct

Description

@bpmct

Extracted from

@bpmct, Asher brought up some great points in another ticket:

  • The readme title should probably match the package name?
  • Seems NPM uses the first line in the readme as the description, but maybe we want an explicit description field in the package.json.
  • Could add keywords in the package.json to make the plugins more discoverable.

Also happy to rename the title if I did it wrong!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0