Tags may not have any characters that encodeuricomponent encodes

npm install fails with EINVALIDTAGNAME, but npm ci does not #1921

Comments

stevenroussey-privicy commented Oct 7, 2020

Current Behavior:

npm install or npm remove fails

Expected Behavior:

Steps To Reproduce:

Environment:

The text was updated successfully, but these errors were encountered:

stevenroussey-privicy commented Oct 7, 2020

The full error is too long to post here.

Also, I tried these steps with same error:

stevenroussey-privicy commented Oct 7, 2020

ljharb commented Oct 7, 2020

Where in your lockfile is pako mentioned?

stevenroussey-privicy commented Oct 7, 2020

Yeah, I see it now. Not sure how that happened.

stevenroussey-privicy commented Oct 7, 2020

stevenroussey-privicy commented Oct 7, 2020

stevenroussey-privicy commented Oct 7, 2020

Oh damn, not even that complicated. I run npm i a second time and it changes it to the broken state.

stevenroussey-privicy commented Oct 7, 2020

So searching through this «fixed» version here is the same are that broke before:

Note that kdbxweb now has a dependencies where before, it did not.

stevenroussey-privicy commented Oct 7, 2020

darcyclarke commented Jun 2, 2021

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team’s discretion as-per our Support Policy.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

Unhandled rejection Error: Invalid tag name ‘-‘: Tags may not have any characters that encodeURIComponent encodes #17049

Comments

Hackwolf commented Jun 7, 2017 •

I’m opening this issue because:

What’s going wrong?

I installed Node.js 8.0.0 on my PC.

My actions are following:

How can the CLI team reproduce the problem?

0 info it worked if it ends with ok
1 verbose cli [ ‘C:\Program Files\nodejs\node.exe’,
1 verbose cli ‘C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js’,
1 verbose cli ‘install’,
1 verbose cli ‘@angular/common’,
1 verbose cli ‘@angular/core’,
1 verbose cli ‘@angular/compiler’,
1 verbose cli ‘—’,
1 verbose cli ‘save’ ]
2 info using npm@5.0.0
3 info using node@v8.0.0
4 silly install loadCurrentTree
5 silly install readLocalPackageData
6 silly fetchPackageMetaData error for @angular/common@latest install [REDACTED] [REDACTED] [REDACTED] — save is not a legal HTTP header value
7 silly fetchPackageMetaData error for @angular/core@latest install [REDACTED] [REDACTED] [REDACTED] — save is not a legal HTTP header value
8 silly fetchPackageMetaData error for @angular/compiler@latest install [REDACTED] [REDACTED] [REDACTED] — save is not a legal HTTP header value
9 error cb() never called!
10 error This is an error with npm itself. Please report this error at:
11 error https://github.com/npm/npm/issues

supporting information:

The text was updated successfully, but these errors were encountered:

[BUG] Some packages can no longer be installed with npm v7 #1734

Comments

debel27 commented Aug 27, 2020

Current Behavior:

Some packages can no longer be installed with NPM v7 (in my case, it’s react-tooltip@3.11.6 )

To me, the install fails for a pretty legitimate reason. Yet, this behavior is not backward compatible.

Here is the relevant log

Expected Behavior:

npm install works flawlessly

Steps To Reproduce:

The text was updated successfully, but these errors were encountered:

mjeanroy commented Aug 28, 2020

I would be happy to submit a PR fixing the issue 😉

ruyadorno commented Sep 4, 2020

mjeanroy commented Sep 13, 2020 •

I made a mistake, my PR fixed a bug with npm cache add command and I made a mistake because the error message was the same.

I don’t think this is really a bug since a non valid semver constraint was probably not officially supported with npm

debel27 commented Sep 13, 2020

I don’t think this is really a bug since a non valid semver constraint was probably not officially supported with npm

isaacs commented Sep 22, 2020

So, the handling of this broken semver range is not actually a breaking change. What changed is that we handle peerDependencies at all, so any broken garbage in a peerDependencies set would have been overlooked in npm v6, and no longer is.

/dev/npm/cli-v6 i # =^16.0.0″: Tags may not have any characters that encodeURIComponent encodes. npm ERR! A complete log of this run can be found in: npm ERR! /Users/isaacs/.npm/_logs/2020-09-22T21_01_59_215Z-debug.log»>

A more extreme example:

The only alternative here would be to catch any invalid data in peerDependencies (but only in peerDependencies), and ignore those peer deps. So then we’d be in a situation where the contract that we install peerDeps is violated.

Another alternative would be that we figure out what >=^16.0.0 means, and add support for that syntax in node-semver. But now we’re playing whack-a-mole with whatever unfiltered garbage happened to land in that previously ignored field.

Yes, packages using this dependency will break, but in this case, I don’t really know if the alternatives are reasonable. Hopefully the users of react-tooltip can update to the fixed version swiftly.

bug: ionic 4.7 update bug #18903

Comments

MrBokeh commented Jul 26, 2019 •

Bug Report

Ionic version:
[x] 4.x

Current behavior:
There are three errors by following the 4.7.0 updating guide:

Second problem, the migrate command doesn’t work:

Expected behavior:

Follow the guide without issues I suppose

Other information:

Ionic info:

The text was updated successfully, but these errors were encountered:

liamdebeasi commented Jul 26, 2019

There is a link in the guide to a known issue in the Angular CLI where the Static Query Migration might not work.

Also for the EINVALIDTAGNAME error it sounds like you may have been missing a space somewhere. I would recommend trying that again, but copying the commands from the migration guide doc.

Can you try that and let me know if it resolves your issue? Thanks!

zmoshansky commented Jul 26, 2019 •

@liamdebeasi @brandyscarney, It may be worth noting in the changelog that Ionic 4.7 brings support for NG8 via #18414.

MrBokeh commented Jul 27, 2019

@liamdebeais, the migration guide causes so much issue with npm modules folder. Eventually I need to delete the npm module folder and the package json lock file.. reinstall everything. Reinstall again with the dev only command. it’s a lot of hassle and still no luck. A lot of packages has mismatch peers etc. The conference app seems to have some matching libraries but the angular 8 has so many breaking changes compare to 7. the import libraries are different etc. I will stick with angular 7 with 4.7.0 until the next starter black project that has angular 8 in it, and then I will migrate my code to 8.

liamdebeasi commented Jul 29, 2019 •

Ionic 4.7.0 is fully compatible with Angular 8 and should not introduce the issues you are describing.

Can you post the steps you are taking to migrate your project to Angular 8? Additionally, if there is an Angular 7 code base you are testing this on, that would also be helpful to see.

npm installation error #173

Comments

devals9 commented Jun 26, 2018

I tried to install bootstrap-social with npm:
npm install bootstrap-social — save

but it gives me error as follows:
npm ERR! code EINVALIDTAGNAME
npm ERR! Invalid tag name «—»: Tags may not have any characters that encodeURIComponent encodes.

npm version: 6.1.0

The error log gives following details:
4 verbose npm-session 7339a5232da192d6
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 silly fetchPackageMetaData error for bootstrap-social@^5.1.1 install bootstrap-social — save is not a legal HTTP header value
8 silly fetchPackageMetaData error for save@latest install bootstrap-social — save is not a legal HTTP header value
9 timing stage:rollbackFailedOptional Completed in 3ms
10 timing stage:runTopLevelLifecycles Completed in 1510ms
11 verbose stack Error: Invalid tag name «—»: Tags may not have any characters that encodeURIComponent encodes.
11 verbose stack at invalidTagName (/usr/local/lib/node_modules/npm/node_modules/npm-package-arg/npa.js:87:15)
11 verbose stack at fromRegistry (/usr/local/lib/node_modules/npm/node_modules/npm-package-arg/npa.js:290:13)
11 verbose stack at resolve (/usr/local/lib/node_modules/npm/node_modules/npm-package-arg/npa.js:77:12)
11 verbose stack at npa (/usr/local/lib/node_modules/npm/node_modules/npm-package-arg/npa.js:48:10)
11 verbose stack at /usr/local/lib/node_modules/npm/lib/install/deps.js:209:14
11 verbose stack at /usr/local/lib/node_modules/npm/node_modules/slide/lib/async-map.js:52:35
11 verbose stack at Array.forEach ()
11 verbose stack at /usr/local/lib/node_modules/npm/node_modules/slide/lib/async-map.js:52:11
11 verbose stack at Array.forEach ()
11 verbose stack at asyncMap (/usr/local/lib/node_modules/npm/node_modules/slide/lib/async-map.js:51:8)
11 verbose stack at exports.getAllMetadata (/usr/local/lib/node_modules/npm/lib/install/deps.js:206:3)
11 verbose stack at Installer.loadArgMetadata (/usr/local/lib/node_modules/npm/lib/install.js:360:3)
11 verbose stack at /usr/local/lib/node_modules/npm/lib/install.js:695:16
11 verbose stack at BB.join.then (/usr/local/lib/node_modules/npm/lib/install/read-shrinkwrap.js:34:16)
11 verbose stack at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
11 verbose stack at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:512:31)
12 verbose cwd /Users/devalshah/TechProjects/justclub/justclub-website
13 verbose Darwin 17.5.0
14 verbose argv «/usr/local/Cellar/node/10.3.0/bin/node» «/usr/local/bin/npm» «install» «bootstrap-social» «—» «save»
15 verbose node v10.3.0
16 verbose npm v6.1.0
17 error code EINVALIDTAGNAME
18 error Invalid tag name «—»: Tags may not have any characters that encodeURIComponent encodes.
19 verbose exit [ 1, true ]

The text was updated successfully, but these errors were encountered: