JedWatson / JedWatson/react-select

React-Select version - 2.4.3 error while npm install

Open
#5,835 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

issue/bug-unconfirmed
Dominant language
TypeScript
Stars
28k
Forks
4.1k
PR merge metrics
No merged PRs in 30d

Description

I am working on a pretty old project and it uses React Select - 2.4.3
We are using Node Version - 6.17.1
and npm version - 3.10.10

it was running smooth until from a few days back, we are having issues in building the frontend for production.

when I run npm install --production , after a while it throws an error. The error is given below.

npm ERR! Linux 6.2.0-39-generic
npm ERR! argv "/home/shahriar/.nvm/versions/node/v6.17.1/bin/node" "/home/shahriar/.nvm/versions/node/v6.17.1/bin/npm" "install" "--production"
npm ERR! node v6.17.1
npm ERR! npm  v3.10.10
npm ERR! path /home/shahriar/aquila-new/PCMS/node_modules/.staging/@types/parse-json-f432fd30/package.json
npm ERR! code ENOTDIR
npm ERR! errno -20
npm ERR! syscall open

npm ERR! ENOTDIR: not a directory, open '/home/shahriar/aquila-new/PCMS/node_modules/.staging/@types/parse-json-f432fd30/package.json'

if I remove the react-select, it will not throw this error. so I am pretty much sure that this issue is triggering because of React-Select.

I have also tried with a brand new package.json file where the only dependency is react-select. This is the package.json file

{
  "name": "select-only",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
          "react-select": "^2.4.3"
  }
}

I used
node version 6.17.1
npm version 3.10.10

It shows the same above error.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure with Node 6.17.1, npm 3.10.10, react-select ^2.4.3, and the minimal package.json shown in the issue. Start with npm install --production and compare the failing node_modules/.staging/@types/parse-json-f432fd30/package.json path; done means the cause is identified and installation succeeds or the incompatibility is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, react
Domain
build-system, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.