Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • C create-react-app
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,547
    • Issues 1,547
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 417
    • Merge requests 417
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Meta
  • create-react-app
  • Issues
  • #753
Closed
Open
Issue created Sep 25, 2016 by Administrator@rootContributor

Forked react-scripts should retain the binary name

Created by: gaearon

Claimed by @shubheksha

People who fork react-scripts shoulldn’t need to rename their bin script because this is annoying. Ideally changing just name in their react-scripts fork’s package.json should be enough.

Looks like #728 made some things better but some things worse. We should keep the part of it where it reads the correct path and removes the correct dependencies, but we should revert the changes to binary names and hardcode react-scripts again there.

Assignee
Assign to
Time tracking