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
  • #1694
Closed
Open
Issue created Mar 02, 2017 by Administrator@rootContributor

existing process using port breaks when username is `cwd`

Created by: chrisdrackett

I feel like this is a regression, but I could be wrong. Because my username is cwd the command to get the process on port 3000 (https://github.com/facebookincubator/create-react-app/blob/05c3b55c62e5b5159382a024c21aa3527c95f1af/packages/react-dev-utils/getProcessForPort.js#L46) ends up spiting out quite a lot of data. While I understand why this is the case, I feel like this command used to work? Did it not used to search for cwd?

Assignee
Assign to
Time tracking