Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npm install error - Invalid tag name ">=^16.0.0" #661

Closed
benbro opened this issue Dec 27, 2020 · 9 comments
Closed

npm install error - Invalid tag name ">=^16.0.0" #661

benbro opened this issue Dec 27, 2020 · 9 comments

Comments

@benbro
Copy link

benbro commented Dec 27, 2020

I'm getting an error when running npm install:

Invalid tag name ">=^16.0.0": Tags may not have any characters that encodeURIComponent encodes.

I'm trying to install this app using:
node.js v15.5.0
npm 7.3.0

npm/cli#1734

@kbokhonko
Copy link

Hi. Have you found a solution for this?

@benbro benbro closed this as completed Feb 23, 2021
@tokomeno-kaltura
Copy link

Having the same problem

before closing the issue please add the solution

@Jaygiri
Copy link

Jaygiri commented Mar 4, 2021

@tokomeno-kaltura try

npm install --legacy-peer-deps

@shapkarin
Copy link

shapkarin commented Sep 5, 2021

@Jaygiri can you please explain why that happens? because I got that error at npm update and does not looks like I can fix it with npm install --legacy-peer-deps

npm update
npm ERR! code EINVALIDTAGNAME
npm ERR! Invalid tag name ">=^16.0.0": Tags may not have any characters that encodeURIComponent encodes.

npm ERR! A complete log of this run can be found in:
...

@Jaygiri
Copy link

Jaygiri commented Sep 6, 2021

@shapkarin I haven't tested --legacy-peer-deps with npm update. May be that fix works for npm install since peer deps where ignored.

It is possible that you have found some issue with npm because as per documentation --legacy-peer-deps should work with npm update.

That said I don't know what was the legacy behavior pre-v7. What you are getting is syntax error ">=^16.0.0" should be ">=16.0.0" and in current version for react-tooltip it is updated.

I would recommend updating to latest version of react-tooltip manually and then running npm update.

@shapkarin
Copy link

shapkarin commented Sep 7, 2021

@Jaygiri make sense, npm i --save react-tooltip@latest helped.

@inerfil
Copy link

inerfil commented Jan 4, 2023

--legacy-peer-deps really works as band-aid, but it has to find a real solution.

@danielbarion
Copy link
Member

Hi @inerfil, this is a closed issue related to V4, if are you having the same problem with V5, please let us know in a new issue, thanks!

@keeganwitt
Copy link

keeganwitt commented Mar 28, 2023

The problem was in the last v3 release here: https://github.com/ReactTooltip/react-tooltip/blob/v3.11.6/package.json#L61-L62
The problem was in v4.0.0 here: https://github.com/ReactTooltip/react-tooltip/blob/v4.0.0/package.json#L61-L62
But it was fixed in v4.0.1: https://github.com/ReactTooltip/react-tooltip/blob/v4.0.1/package.json#L60-L61

See the 4.0.1 release notes, which reference the fix in f30ae74.

An override might be a way to work around this issue or just upgrade to 4.0.1 or later.

@ReactTooltip ReactTooltip locked and limited conversation to collaborators Mar 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants