npm ERR! Cannot read properties of null (reading 'pickAlgorithm')

Question

iam getting below error with npm while creating react app

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\Nagamanickam\AppData\Local\npm-cache_logs\2021-11-18T12_01_45_525Z-debug.log

Does this answer your question? [Getting "Cannot read property 'pickAlgorithm' of null" error in react native](https://stackoverflow.com/questions/69567381/getting-cannot-read-property-pickalgorithm-of-null-error-in-react-native) — Fiodorov Andrei, Nov 22 '21 at 10:11
ere is something very similar asked before: [enter link description here](https://stackoverflow.com/questions/69567381/getting-cannot-read-property-pickalgorithm-of-null-error-in-react-native) — Kiana Kazeminejad, Jan 04 '22 at 13:34

score 16 · Answer 1 · answered Dec 30 '21 at 20:48

16

my npm version is 8.1.4 and i solve this problem by running :

npm cache clear --force

answered Dec 30 '21 at 20:48

Nachat Ayoub

359
2
8

29

didn't solve it for me – dialex Feb 09 '22 at 15:51
Didn't work for me too – Rahul Dudhane Feb 23 '22 at 06:19
Did not work for me as well – Vishal Singh Jan 13 '23 at 07:37
Didn't work for me either – ataraxia Mar 01 '23 at 15:01
1

Fixed it for me! – Ragav Y Apr 21 '23 at 12:08

score 14 · Answer 2 · answered Feb 07 '22 at 17:38

14

I resolved it by deleting node_modules and package-lock.json and run npm install again.

answered Feb 07 '22 at 17:38

Nils Reichardt

3,195
2
18
28

10

didn't solve it for me – dialex Feb 09 '22 at 15:51
Didn't work for me too – Rahul Dudhane Feb 23 '22 at 06:20
Problem for me was in Jenkins Builds only, local builds were successful. The cause was that we do commit package-lock.json. In the build Jenkins appends the build-no to version in package.json. This way package.json and package-lock.json were inconsistent and npm install failed. The solution was to delete package-lock.json prior to npm install. – Zaphod Beeblebrox Jul 10 '23 at 12:26
This worked for me thank you! – Anarkie Aug 01 '23 at 09:55

score 9 · Answer 3 · answered Oct 17 '22 at 17:45

9

solved with npm i --legacy-peer-deps on react-native version .70

answered Oct 17 '22 at 17:45

Engr.Aftab Ufaq

3,356
3
21
47

score 7 · Answer 4 · answered Jul 18 '22 at 11:29

7

Just run these 2 commands :

npm cache clear --force
npm install

answered Jul 18 '22 at 11:29

torq1284

101
1
7

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Jul 19 '22 at 18:31

Ahmedakhtar11 · Answer 5 · 2022-03-16T21:24:19.297

3

Probably it's a project that works with Yarn and not NPM. Try Yarn instead of NPM.

yarn install

and then you can do

yarn start

or

npm start

edited Mar 16 '22 at 21:24

answered Mar 16 '22 at 21:02

Ahmedakhtar11

1,076
11
7

score 2 · Answer 6 · answered Dec 09 '22 at 08:31

2

In my case i updated npm via:

npm update -g npm

After it, everything worked fine.

Don't know why, i didn't expect it.

answered Dec 09 '22 at 08:31

Elleshar

63
6

score 1 · Answer 7 · answered Nov 20 '22 at 06:54

1

Your dependency tree may be broken (due to incompartible peer dependencies) you can try running npm install with --legacy-peer-deps or --force to bypass this issue for the mean time.

answered Nov 20 '22 at 06:54

Chisom Maxwell

149
2
7

score 1 · Answer 8 · answered Mar 15 '23 at 21:36

1

If you have this issue on the CI:

$ npm ci
npm ERR! Cannot read property '<any-package-here>' of undefined

You should check the version of Nodeon the CI. It was outdated for me.

answered Mar 15 '23 at 21:36

Ambroise Rabier

3,636
3
27
38

This saved my time. I found that I used the version of Node which isn't matched with the requirement in the package.json. – Phin May 26 '23 at 09:38

score 0 · Answer 9 · answered May 12 '22 at 05:34

0

In my case the file .npmrc was corrupt. After deleting it everything worked.

answered May 12 '22 at 05:34

Simon Martinelli

34,053
5
48
82

where .npmrc can be found? – osama Jun 01 '22 at 21:01
In your home directory – Simon Martinelli Jun 04 '22 at 21:32

score 0 · Answer 10 · answered Jul 06 '22 at 17:26

0

I was getting the same error, but I was able to resolve it by the below described method:

Go to folder -> Local > npm-cache and delete all contents of the npm-cache. try again with npm command, it should work now.

answered Jul 06 '22 at 17:26

Ankit Awadhiya

11
1

score 0 · Answer 11 · answered Nov 12 '22 at 13:37

0

I solved this by update npm from 6.x to 8.5x, then run npm cache clear --force, npm install, however, it has to change the nodejs from 14 to 17, my env is macOS m1 pro.

answered Nov 12 '22 at 13:37

miya jake

11

score 0 · Answer 12 · answered Dec 06 '22 at 22:33

0

I was getting this error from an old branch that had a previous version of node/npm. using the correct version of node helped in my case.

answered Dec 06 '22 at 22:33

Ju An Kang

29
2

score -1 · Answer 13 · answered Jan 09 '23 at 11:23

-1

I solved deleting node_modules and running this command:

npm cache clear --force

answered Jan 09 '23 at 11:23

Miguel Angel

944
8
20

score -1 · Answer 14 · answered Mar 14 '23 at 03:06

-1

If you were encountering this problem while using NPM workspaces, try removing all of the node_modules directory that is not the root one. Such as:

$ rm -rf packages/*/node_modules
$ npm install

answered Mar 14 '23 at 03:06

nil

3,421
2
21
21

npm ERR! Cannot read properties of null (reading 'pickAlgorithm')

14 Answers14

Linked