# Struggling to Diagnose "Error: Invalid tag name '\>=^16.0.0'"

**URL:** <https://mediasoup.discourse.group/t/struggling-to-diagnose-error-invalid-tag-name-16-0-0/2637>\
**Category:** mediasoup-demo\
**Created:** [March 28, 2021, 5:32pm UTC](https://mediasoup.discourse.group/t/struggling-to-diagnose-error-invalid-tag-name-16-0-0/2637 "2021-03-28T17:32:07Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Meeshbhoombah](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/meeshbhoombah/32/912_2.png) [@Meeshbhoombah](https://mediasoup.discourse.group/u/Meeshbhoombah)\
**Post date:** [March 28, 2021, 5:32pm UTC](https://mediasoup.discourse.group/t/struggling-to-diagnose-error-invalid-tag-name-16-0-0/2637/1 "2021-03-28T17:32:07Z")

</div>

I’m building the [mediasoup-demo on the v3 branch](https://github.com/versatica/mediasoup-demo), after cloning it to my local system. I’m using npm version 7.6.2.

The server builds fine if I do `npm i` in `/server`, but I’m getting this error when I `cd` into `app` and try to do `npm i` there.

```auto
136 timing command:i Completed in 4723ms
137 verbose stack Error: Invalid tag name ">=^16.0.0": Tags may not have any characters that encodeURIComponent encodes.
137 verbose stack at invalidTagName (/usr/local/lib/node_modules/npm/node_modules/npm-package-arg/npa.js:94:15)
137 verbose stack at fromRegistry (/usr/local/lib/node_modules/npm/node_modules/npm-package-arg/npa.js:299:13)
137 verbose stack at Function.resolve (/usr/local/lib/node_modules/npm/node_modules/npm-package-arg/npa.js:84:12)
137 verbose stack at Arborist.[nodeFromEdge] (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:899:37)
137 verbose stack at async Arborist.[loadPeerSet] (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1107:23)
137 verbose stack at async Arborist.[buildDepStep] (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:838:11)
137 verbose stack at async Arborist.buildIdealTree (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:209:7)
137 verbose stack at async Promise.all (index 1)
137 verbose stack at async Arborist.reify (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:131:5)
137 verbose stack at async Install.install (/usr/local/lib/node_modules/npm/lib/install.js:120:5)
138 verbose cwd /Users/akm/mediasoup-demo/app
139 verbose Darwin 19.6.0
140 verbose argv "/usr/local/Cellar/node/15.10.0/bin/node" "/usr/local/bin/npm" "i"
141 verbose node v15.10.0
142 verbose npm v7.6.2
143 error code EINVALIDTAGNAME
144 error Invalid tag name ">=^16.0.0": Tags may not have any characters that encodeURIComponent encodes.

```

I tried finding an occurrence of `">=16.0.0"` in the project, via GitHub and my local system, but couldn’t find where that exists.

Is this an issue with my version of `npm`?

* * *

Since this is my first post on the forum I would like to take the opportunity to say thanks to everyone who contributes to the discussion and the project 🙏

---

<div class="post-metadata">

**Author:** ![jmillan](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/jmillan/32/9_2.png) [@jmillan](https://mediasoup.discourse.group/u/jmillan)\
**Post date:** [March 29, 2021, 7:05am UTC](https://mediasoup.discourse.group/t/struggling-to-diagnose-error-invalid-tag-name-16-0-0/2637/2 "2021-03-29T07:05:15Z")

</div>

> [@Meeshbhoombah](#):
>
> `Arborist`

`arborist` or `npa` is not present in mediasoup-demo. It must be something in your local setup.

---

<div class="post-metadata">

**Author:** ![Meeshbhoombah](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/meeshbhoombah/32/912_2.png) [@Meeshbhoombah](https://mediasoup.discourse.group/u/Meeshbhoombah)\
**Post date:** [April 2, 2021, 1:24am UTC](https://mediasoup.discourse.group/t/struggling-to-diagnose-error-invalid-tag-name-16-0-0/2637/3 "2021-04-02T01:24:59Z")

</div>

I see - I didn’t set my current system up for development, so there may be some issues there as a result.

I’ll be trying to fix this over the weekend - will first try a different version of npm to see if that helps (this is because, after some Googling, I found that Arborist “[is the dependency tree manager for npm, new in npm v7](https://blog.npmjs.org/post/618653678433435649/npm-v7-series-arborist-deep-dive.html)”).

If that doesn’t work, I’ve got other additional reasons to reset my system, so I’ll try that as well.

---

<div class="post-metadata">

**Author:** ![louxiu](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/louxiu/32/1071_2.png) [@louxiu](https://mediasoup.discourse.group/u/louxiu)\
**Post date:** [June 28, 2021, 6:32am UTC](https://mediasoup.discourse.group/t/struggling-to-diagnose-error-invalid-tag-name-16-0-0/2637/4 "2021-06-28T06:32:28Z")

</div>

You can use `npm install --legacy-peer-deps`.

Ref: [[BUG] Some packages can no longer be installed with npm v7 · Issue #1734 · npm/cli · GitHub](https://github.com/npm/cli/issues/1734)

---

<div class="post-metadata">

**Author:** ![chenzx](https://avatars.discourse-cdn.com/v4/letter/c/ee59a6/32.png) [@chenzx](https://mediasoup.discourse.group/u/chenzx)\
**Post date:** [August 2, 2021, 7:17am UTC](https://mediasoup.discourse.group/t/struggling-to-diagnose-error-invalid-tag-name-16-0-0/2637/5 "2021-08-02T07:17:23Z")

</div>

> [@louxiu](#):
>
> npm install --legacy-peer-deps

i got the same problem when try `npm i gulp` with node 14, this helps!
