Error when i install

[ElBidouilleur]

HI

When I update all package in my project

`
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! coa@2.1.3 preinstall: start /B node compile.js & node compile.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the coa@2.1.3 preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/mboutin/.npm/_logs/2021-11-04T14_01_45_544Z-debug.log
`

[okkindel]

duplicate #99

[mizhon]

Get the same error when I saw the new version was published.

And now I find they fix it.

[ShenganLee]

Same question

[jacksaad1991]

I don't see this removal that @mizhon has mentioned, when i go to NPM I still see it like this:

[wuyuchang]

The author has deleted the package.

[wuyuchang]

Get the same error when I saw the new version was published.

And now I find they fix it.

npm install coa@2.0.2
and make sure that package.json doesn't have ^ in front of the version. package-lock.json will be better

[ihsanakcali]

is there any way to publish new version of this dependency?

[ihsanakcali]

i need new version because 2.1.3 corrupted and it was latest of major 2

[yarastqt]

@crashday Hello, currently latest version is 2.0.2, you can check via npm cli:

λ ~ npm info coa

coa@2.0.2 | MIT | deps: 3 | versions: 29
Command-Option-Argument: Yet another parser for command line options.
http://github.com/veged/coa

dist
.tarball: https://registry.npmjs.org/coa/-/coa-2.0.2.tgz
.shasum: 43f6c21151b4ef2bf57187db0d73de229e3e7ec3
.integrity: sha512-q5/jG+YQnSy4nRTV4F7lPepBJZ8qBNJJDBuJdoejDyLXgmL7IEo+Le2JDZudFTFt7mrCqIRaSjws4ygRCTCAXA==
.unpackedSize: 72.5 kB

dependencies:
@types/q: ^1.5.1 chalk: ^2.4.1    q: ^1.1.2

maintainers:
- qfox <dazper88@protonmail.com>

dist-tags:
latest: 2.0.2

published over a year ago by qfox <zxqfox@gmail.com>

UPD. If you see another version, you can try to clean cache: npm cache clean --force

[ihsanakcali]

Hi @yarastqt, thank you.
i use private nexus npm-proxy registry and it indexed coa 3.01 and 2.1.3. Everytime i try to build new package on CI/CD pipeline it fails because it tries to pull coa 2.1.3

[FeSeason]

Deleting packages is not a good way. They will be cached in internal nodes, such as verdaccio and nexus. It is recommended to upgrade directly

[yufengwang]

how to sync coa with verdaccio ?

[zhuCheer]

Get the same error

[tcstory]

same error

[yufengwang]

@FeSeason For using verdaccio, just manual remove coa in storage folder fix this problem.

[FeSeason]

@FeSeason For using verdaccio, just manual remove coa in storage folder fix this problem.

already did.

[ihsanakcali]

2.1.3 removed but it is still in the index https://registry.npmjs.org/coa , who can fix it?

[marcorosa]

Some versions of this package have been removed because they contained malicious code. More context here.

[ihsanakcali]

i managed to update my npm proxy index with npm dist-tag coa command, my problem solved

[darioseidl]

I was getting an error too when I run yarn install, on a project that indirectly depends on coa@^2.0.2.

yarn install v1.22.10
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/coa/-/coa-2.0.4.tgz: Request failed \"404 Not Found\"".
info If you think this is a bug, please open a bug report with the information provided in "/home/dario/Projekte/MediPrime/mp/mp-ui/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

I can work around this issue, by putting

  "resolutions": {
    "coa": "2.0.2"
  }

in my package.json.

It seems that version 2.0.4 was deleted from the npm and yarn repos because it contained malicious code. To solve resolutions of the ^2.0.2 range, a real fix would be to upload a proper version in that range, e.g. a 2.0.5 (even if it's the same code as 2.0.2). And a 2.1.4 for the removed 2.1.3 respectively.

[avtokey]

I have same error on Angular project, Can everyone tell me fix way ? "resolutions" and other solutions doesn't works

[darioseidl]

@avtokey Are you using npm or yarn (or something else)? Do you have a direct dependency on coa in your package.json or just some other package that depends on coa? What error do you get exactly?

[latel]

I was getting an error too when I run yarn install, on a project that indirectly depends on coa@^2.0.2.

yarn install v1.22.10
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/coa/-/coa-2.0.4.tgz: Request failed \"404 Not Found\"".
info If you think this is a bug, please open a bug report with the information provided in "/home/dario/Projekte/MediPrime/mp/mp-ui/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

I can work around this issue, by putting

  "resolutions": {
    "coa": "2.0.2"
  }

in my package.json.

It seems that version 2.0.4 was deleted from the npm and yarn repos because it contained malicious code. To solve resolutions of the ^2.0.2 range, a real fix would be to upload a proper version in that range, e.g. a 2.0.5 (even if it's the same code as 2.0.2). And a 2.1.4 for the removed 2.1.3 respectively.

"resolutions": {
    "coa": "2.0.2"
  }

solves the problem, no idea which package is depending on coa-2.1.3

[tianfengbiao]

same problem

[avtokey]

@darioseidl Yes, I use NPM, I don't have direct reference on my pckage.json, It seems some other package needs COA. Error: 404 Not Found - coa-2.1.3.tgz

[darioseidl]

With yarn you can use yarn why coa to find out which package depends on it, and yarn supports resolutions in the package.json.

npm doesn't have either, but you can try with third-party packages: npm-why and npm-force-resolutions. I haven't tried them myself, but they sound like the right thing for the job.