storybookjs/storybook

[Documentation]: Incorrect homepage and repository.directory paths in @storybook/cli package.json

Open

#31,800 opened on Jun 17, 2025

View on GitHub
 (4 comments) (0 reactions) (0 assignees)TypeScript (10,058 forks)batch import
documentationhelp wanted

Repository metrics

Stars
 (89,909 stars)
PR merge metrics
 (Avg merge 9d 3h) (173 merged PRs in 30d)

Description

Describe the problem

Currently, the homepage and repository.directory fields in the package.json files for both the @storybook/cli package (code/lib/cli-storybook/package.json) and the sb package (code/lib/cli-sb/package.json) are pointing to code/lib/cli, but they should point to code/lib/cli-storybook.

Problem

  • The homepage is set to https://github.com/storybookjs/storybook/tree/next/code/lib/cli
  • The repository.directory is set to code/lib/cli

Suggested Fix

  • Update both fields to point to code/lib/cli-storybook

Affected Files

  • code/lib/cli-storybook/package.json
  • code/lib/cli-sb/package.json

Notes

  • This is a metadata fix only and does not affect functionality, but it is important for accuracy and maintainability.

Additional context

No response

Contributor guide

Research direction
Locate the files code/lib/cli storybook/package.json and code/lib/cli sb/package.json. In each file, update the 'homepage' field from 'https://github.com/storybookjs/storybook/tree/next/code/lib/cli' to 'https://github.com/storybookjs/storybook/tree/next/code/lib/cli storybook' and the 'repository.directory' field from 'code/lib/cli' to 'code/lib/cli storybook'. No functional changes are needed.
Tech stack
typescriptnodejs
Domain
documentationdeveloper experience
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Basic JSON knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
95