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
  • #970
Closed
Open
Issue created Oct 27, 2016 by Administrator@rootContributor

Long path support issues on windows when using npm3

Created by: gertjvr

Description

TL;DR when using npm3 node packages should not include their dependencies. ie shouldn't have a sub node_modules folder. on windows this can cause long path names. longer than what windows can support. npm guidance https://docs.npmjs.com/how-npm-works/npm3

Long story but we use cake build scripts and it doesn't support long files paths on windows. We have had a similar issue recently when phantomjs broken release.

Environment

  1. npm ls react-scripts (if you haven’t ejected): react-scripts@0.7.0
  2. node -v: v4.4.5 / v6.9.1
  3. npm -v: v3.7.1 / v3.10.8

Then, specify:

  1. Operating system: Windows 10 and Windows Server 2012

node_modules structure after npm install

Assignee
Assign to
Time tracking