Npm Error - No matching version found for

Question

i clone a project with git, the project was create with ionic 2 but when i execute the command for re-create the node_modules folder i get this error.

npm install
npm WARN deprecated [email protected]: Please update to the latest object-keys
npm ERR! code ETARGET
npm ERR! notarget No matching version found for ionic-native@^3.5.0
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget 
npm ERR! notarget It was specified as a dependency of 'ionic-hello-world'
npm ERR! notarget 

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/wihermes/.npm/_logs/2017-06-02T13_58_47_295Z-debug.log

NOTE: I already update npm.

Does anyone know how to fix it?

Same problem now after npm install -g ionic@latest which takes it up to v.3.12.0 ... npm complains that there "is no matching version found", but it's clearly installed. Worked to change package.json to target `"^3.0.0" and then let it install whatever it wanted to. That apparently worked, but it only installed 3.10.3. No idea why the difference, but meh. — mc01
– mc01, Commented Oct 1, 2017 at 16:56

Brij · Accepted Answer · 2021-03-01 19:05:27Z

275

I was having issue for a package which was available. Force cleaning the cache helped.

npm cache clean --force

answered Mar 1, 2021 at 19:05

Brij

13.4k23 gold badges85 silver badges119 bronze badges

Sign up to request clarification or add additional context in comments.

8 Comments

silverwind Over a year ago

Helped as well. Seems like a corrupted cache is the most likely reason for this error on npm v7.

Jafar Amini Over a year ago

Use sudo before the command.

Janet Over a year ago

I have npm 8.1.2 and was trying to install newer version of angualr cli, got an error saying "No matching version found for [email protected].". This command helped.

Holger Ludvigsen Over a year ago

Without --force I got the message:

As of npm@5, the npm cache self-heals from corruption issues by treating integrity mismatches as cache misses.  As a result, data extracted from the cache is guaranteed to be valid.

But the problem was still fixed by forcing a cache clean! So much for the bold statements in the warning.

Mormegil Over a year ago

For me, just npm cache verify seems to have helped. (Even though its output did not signal anything like a problem would have been found.)

|

Peter Reid · Accepted Answer · 2023-06-07 10:15:45Z

95

The version you have specified, or one of your dependencies has specified is not published to npmjs.com

Executing npm view ionic-native versions (see docs) the following output is returned for package versions:

versions:
   [ '1.0.7',
     '1.0.8',
     '1.0.9',
     '1.0.10',
     '1.0.11',
     '1.0.12',
     '1.1.0',
     '1.1.1',
     '1.2.0',
     '1.2.1',
     '1.2.2',
     '1.2.3',
     '1.2.4',
     '1.3.0',
     '1.3.1',
     '1.3.2',
     '1.3.3',
     '1.3.4',
     '1.3.5',
     '1.3.6',
     '1.3.7',
     '1.3.8',
     '1.3.9',
     '1.3.10',
     '1.3.11',
     '1.3.12',
     '1.3.13',
     '1.3.14',
     '1.3.15',
     '1.3.16',
     '1.3.17',
     '1.3.18',
     '1.3.19',
     '1.3.20',
     '1.3.21',
     '1.3.22',
     '1.3.23',
     '1.3.24',
     '1.3.25',
     '1.3.26',
     '1.3.27',
     '2.0.0',
     '2.0.1',
     '2.0.2',
     '2.0.3',
     '2.1.2',
     '2.1.3',
     '2.1.4',
     '2.1.5',
     '2.1.6',
     '2.1.7',
     '2.1.8',
     '2.1.9',
     '2.2.0',
     '2.2.1',
     '2.2.2',
     '2.2.3',
     '2.2.4',
     '2.2.5',
     '2.2.6',
     '2.2.7',
     '2.2.8',
     '2.2.9',
     '2.2.10',
     '2.2.11',
     '2.2.12',
     '2.2.13',
     '2.2.14',
     '2.2.15',
     '2.2.16',
     '2.2.17',
     '2.3.0',
     '2.3.1',
     '2.3.2',
     '2.4.0',
     '2.4.1',
     '2.5.0',
     '2.5.1',
     '2.6.0',
     '2.7.0',
     '2.8.0',
     '2.8.1',
     '2.9.0' ],

As you can see no version higher than 2.9.0 has been published to the npm repository. Strangely they have versions higher than this on GitHub. I would suggest opening an issue with the maintainers on this.

For older versions of npm, the command may be npm view ionic-native (see legacy docs)

For now you can manually install the package via the tarball URL of the required release:

npm install https://github.com/ionic-team/ionic-native/tarball/v3.5.0

edited Jun 7, 2023 at 10:15

answered Jun 2, 2017 at 15:27

Peter Reid

5,5072 gold badges39 silver badges33 bronze badges

4 Comments

Master Yoda Over a year ago

Can you tell me about bp-datepicker , i can see version 5.0.6 is the latest but when i try to install it , it only installs 4.0.6 as the letest .

Peter Reid Over a year ago

Don't see how this relates back, open a new question please @MasterYoda

trebor Over a year ago

We faced this issue in our organization when using Nexus for npm dependencies. The versions for packages were stale, so our workaround is to "Invalidate cache" on the Nexus repository.

Cameron Hudson Over a year ago

As of npm v8, the command now seems to be npm view ionic-native versions.

Olegas Gončarovas · Accepted Answer · 2023-10-15 16:45:41Z

66

Try removing package-lock.json file first.

2023-10-15 NOTICE:

As other users mentioned this is not a good solution. Use this only as a last resort.

edited Oct 15, 2023 at 16:45

answered Feb 7, 2018 at 17:36

Olegas Gončarovas

1,6671 gold badge12 silver badges16 bronze badges

4 Comments

Chilian Over a year ago

This is no solution at all! Removing the lock file is like updating most packages to the latest known version. In worst case you have no tests within your project. Then you have to check every little functionality manually to verify everything still works fine.

Nicolas R Over a year ago

this worked for me whenI got a similar error after I changed the name in package.json

GeorgeButter Over a year ago

I was trying to install a version that did exist. I confirmed it did exist using npm view. For some reason this worked for me.

Jimmy Over a year ago

It worked for me when I updated node and angular cli version.

BuZZ-dEE · Accepted Answer · 2021-07-28 09:06:41Z

17

Try removing package-lock.json and running npm install && npm update, it'll install the latest version and clear all errors.

edited Jul 28, 2021 at 9:06

BuZZ-dEE

7,15316 gold badges75 silver badges105 bronze badges

answered May 24, 2018 at 8:26

Lai Xue

1,5811 gold badge15 silver badges17 bronze badges

1 Comment

Rohit Kumar Over a year ago

Removing the lock file is like updating most packages to the latest known version, which may not help rather than create more errors by installing packages which are not backwards compatible

Utmost Creator · Accepted Answer · 2022-01-13 14:22:22Z

9

In my case I was needed to do the following steps: The 1st step is outdated, so it could be skipped (most probably)

npm cache clean --force
npm cache verify
npm uninstall yourPackage
npm uninstall -g yourPackage

My problem is described here

After these steps the application was generated successfully.

answered Jan 13, 2022 at 14:22

Utmost Creator

1,1691 gold badge13 silver badges26 bronze badges

Comments

Ahmed Mansour · Accepted Answer · 2023-06-13 06:04:08Z

8

coming from the future to add one point:

Thanks what other people mentioned we have:

you should try clearing cache npm cache clean --force
and view the versions npm view [pacakgeName] versions

What I wanted to add:

if it didn't work, check you registry npm config get registry and make sure it matches this https://registry.npmjs.org/

The last point was my problem, So wanted to mention it in case someone had same problem.

answered Jun 13, 2023 at 6:04

Ahmed Mansour

6107 silver badges16 bronze badges

Comments

Divin Irakiza · Accepted Answer · 2021-11-05 06:05:35Z

5

To solve the issue:

Delete your package-lock.json or yarn.lock

Run npm cache clean --force

Then npm install or yarn install again.

answered Nov 5, 2021 at 6:05

Divin Irakiza

3672 silver badges7 bronze badges

1 Comment

Dirk Schumacher Over a year ago

Cleaning the cache helped me. There was no package-lock-.json anyways.

Dinushan Paranavithana · Accepted Answer · 2024-02-01 11:27:26Z

3

npm ERR! code ETARGET

npm ERR! notarget No matching version found for vue@next.

npm ERR! notarget In most cases you or one of your dependencies are requesting

npm ERR! notarget a package version that doesn't exist.

I got this error when I tried to install vue on a laravel 10 project with nodejs at v20.11.0

instead of using

npm install vue@next

I used

npm install vue@latest

and this solved the issue !

answered Feb 1, 2024 at 11:27

Dinushan Paranavithana

511 bronze badge

Comments

Per Quested Aronsson · Accepted Answer · 2018-06-14 07:15:44Z

2

Removing package-lock.json should be the last resort, at least for projects that have reached production status. After having the same error as described in this question, I found that my package-lock.json was corrupt, even though it was generated. One of the packages had itself as an empty dependency, in this example jsdoc:

        "jsdoc": {
        "version": "x.y.z",
        . . . . . . 
        "dependencies": {
            . . . . . ,
            "jsdoc": {},
            "taffydb": {
             . . . . .

Please note I have omitted irrelevant parts of the code in this example.

I just removed the empty dependency "jsdoc": {}, and it was OK again.

answered Jun 14, 2018 at 7:15

Per Quested Aronsson

12.2k8 gold badges58 silver badges77 bronze badges

1 Comment

cloakedninjas Over a year ago

I had this too - even after running npm install with no package-lock.json ... Had to blow out node_modules and do another npm install to finally get this fixed

isaura almar · Accepted Answer · 2018-08-10 09:19:17Z

2

Probably not the case of everybody but I had the same problem. I was using the last, in my case, the error was because I was using jfrog manage from the company where I am working.

 npm config list

The result was

; cli configs
metrics-registry = "https://COMPANYNAME.jfrog.io/COMPANYNAM/api/npm/npm/"
scope = ""
user-agent = "npm/6.3.0 node/v8.11.2 win32 x64"

; userconfig C:\Users\USER\.npmrc
always-auth = true
email = "XXXXXXXXX"
registry = "https://COMPANYNAME.jfrog.io/COMPANYNAME/api/npm/npm/"

; builtin config undefined
prefix = "C:\\Users\\XXXXX\\AppData\\Roaming\\npm"

; node bin location = C:\Program Files\nodejs\node.exe
; cwd = C:\WINDOWS\system32
; HOME = C:\Users\XXXXXX
; "npm config ls -l" to show all defaults.

I solve the problem by using the global metrics.

answered Aug 10, 2018 at 9:19

isaura almar

4961 gold badge5 silver badges14 bronze badges

1 Comment

Donald33 Nevermore Over a year ago

I changed the registry back to default, and it worked.

Aliti · Accepted Answer · 2021-02-28 02:22:16Z

2

try

npm install --force
npm install --legacy-peer-deps

answered Feb 28, 2021 at 2:22

Aliti

2,1152 gold badges27 silver badges40 bronze badges

Comments

Davide Calarco · Accepted Answer · 2022-08-18 14:33:23Z

2

For me the problem was that I issued the command:

npm publish dist

While this other command works:

npm publish dist/

The log was not intuitive.

answered Aug 18, 2022 at 14:33

Davide Calarco

5424 silver badges6 bronze badges

1 Comment

SwissCoder Over a year ago

oh man, this... after wasting hours this did the trick! seems this somewhen changed between older versions of node.js if you user 16 or newer I guess this change is required

Fauzan Edris · Accepted Answer · 2025-04-17 04:01:03Z

For those who have already run npm cache clean --force but are still facing issues, please check the list of versions available for the package you are trying to install. You can do this by using the command:

npm view <package> versions.

After running this command, you will see a list of versions for that package. Please compare this list with the one shown on the NPM website.

https://www.npmjs.com/

If you do not see the latest version in that list, you might want to verify which registry you're using. You can check it by running:

npm config get registry.

By default, the npm registry should be:

https://registry.npmjs.org/

If the registry you're using is not the default one, change it by running:

npm config set registry <url>

or

npm config set registry http://registry.npmjs.org/.

Hope this helps.

UPDATE || 17 April 2025

If you are using a registry mirror such as:

https://npmmirror.com/

On the package page, you can click the 进行同步 button to notify npmmirror to update their data. Wait a moment after clicking that button, and npmmirror will provide the latest version. After npmmirror updates their data, you can try running npm install again.

Pete Hayman · Accepted Answer · 2021-07-23 03:42:07Z

0

For those experimenting with creating their own packages, make sure that you dont skip a version. For instance, if I have published my-package 1.0.1 & 1.0.3, when I go to install it from elsewhere I will get an error notarget No matching version found for [email protected].

The good news is it is fairly easy to fix, simply 'backfill' the empty version.

edit package.json -> "version": "1.0.2"
npm publish

EDIT: As suggested in comment, clearing the cache will solve the problem locally

npm cache clean --force

edited Jul 23, 2021 at 3:42

answered Jul 7, 2021 at 6:05

Pete Hayman

6,1152 gold badges44 silver badges49 bronze badges

1 Comment

birnchen7 Over a year ago

had the same situation, clearing the cache with npm cache clean --force did the trick as explained below from @Brij

Laurent Keusch · Accepted Answer · 2022-05-10 07:37:30Z

0

Haven't seen it mentionned yet, for me it was my project's .npmrc file that was pointing to the wrong npm registry, as we're using Azure DevOps Package Registry.

answered May 10, 2022 at 7:37

Laurent Keusch

5187 silver badges17 bronze badges

Comments

Dwain B · Accepted Answer · 2023-05-12 18:45:40Z

0

I and running a node app with nextjs on the frontend and nestjs on the backend.

What I did was to delete my pnpm-lock.yaml file from my project folder and I was able to get past this error. It did went ahead and re-create this file though.

answered May 12, 2023 at 18:45

Dwain B

1971 silver badge6 bronze badges

Comments

Moshisho · Accepted Answer · 2023-06-07 16:38:33Z

0

In my case, I was trying to install yarn@3, running npm view yarn showed version 3 isn't on npm.

Going to the yarn docs for version 3 showed the solution:

corepack prepare yarn@stable --activate
corepack prepare yarn@<version> --activate

answered Jun 7, 2023 at 16:38

Moshisho

3,0411 gold badge25 silver badges43 bronze badges

Comments

Komal · Accepted Answer · 2023-07-27 18:34:23Z

0

Inside your package.json, delete "graphql": "^", and npm install after saving the changes

answered Jul 27, 2023 at 18:34

Komal

111 bronze badge

1 Comment

Community Over a year ago

As it’s currently written, your answer is unclear. Please edit to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers in the help center.

DoloreMentale · Accepted Answer · 2020-10-01 18:00:08Z

-1

If none of this did not help, then try to swap ^ in "^version" to ~ "~version".

answered Oct 1, 2020 at 18:00

DoloreMentale

114 bronze badges

Comments

Enrico Cortinovis · Accepted Answer · 2021-01-03 02:05:21Z

-2

first, in C:\users\your PC write npm uninstall -g create-react-app then, create your project folder with npx create-react-app folder-name.

edited Jan 3, 2021 at 2:05

Enrico Cortinovis

8913 gold badges11 silver badges35 bronze badges

answered Jan 2, 2021 at 9:42

musa23

1

Comments

Super Kai - Kazuya Ito · Accepted Answer · 2022-02-11 07:30:37Z

-2

Remove node_modules, cache files (normally are at the top of the folder in your editor) and the package-lock.json, then run npm install.

edited Feb 11, 2022 at 7:30

Super Kai - Kazuya Ito

42.7k23 gold badges257 silver badges256 bronze badges

answered Feb 8, 2022 at 2:38

Luis Lopez

111 bronze badge

Collectives™ on Stack Overflow

Npm Error - No matching version found for

21 Answers 21

8 Comments

4 Comments

4 Comments

1 Comment

Comments

Comments

1 Comment

Comments

1 Comment

1 Comment

Comments

1 Comment

UPDATE || 17 April 2025

Comments

1 Comment

Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

21 Answers 21

8 Comments

4 Comments

4 Comments

1 Comment

Comments

Comments

1 Comment

Comments

1 Comment

1 Comment

Comments

1 Comment

UPDATE || 17 April 2025

Comments

1 Comment

Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related