Skip to content

Minor: Empty Package Name in package.json #19

@AliiiBenn

Description

@AliiiBenn

Priority

🟡 Minor - Package Metadata

Location

package.json:2

Problem Description

The package name is an empty string and the description says "A blank template to get started with Payload 3.0".

Issues

1. Package Management Problems

NPM warnings about missing name, description, repository field.

2. Lockfile Confusion

  • pnpm-lock.yaml references empty name
  • Hard to identify in node_modules
  • Dependency tree unclear

3. Publishing Issues

Cannot publish to npm (name required)

4. Metadata Accuracy

  • Description says "blank template"
  • Version is 1.0.0 but this is active development
  • Repository field missing

Expected package.json

Add proper package name (python-secrets), update version to 0.1.0 (initial development), update description to match project, add repository field, keywords, and URLs.

Version Number

Current: 1.0.0
Recommended: 0.1.0

Semantic Versioning for unstable software:

  • 0.x.y = Initial development
  • 1.0.0 = First stable release
  • This is clearly not stable yet (see issues list!)

Steps to Fix

  1. Add package name: python-secrets
  2. Update version to 0.1.0
  3. Update description to match project
  4. Add repository field
  5. Add keywords
  6. Add bugs/homepage URLs
  7. Remove generic description

Additional Context

This appears to be a leftover from the Payload CMS template. The description "A blank template to get started with Payload 3.0" confirms this. Should be updated to reflect the actual project.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions