Skip to content

Wrong versions for karma-coverage and karma-jasmine-html-reporter. #223

@VictosVertex

Description

@VictosVertex

Hey,

I think the last version updates introduced wrong versions for the packages karma-coverage and karma-jasmine-html-reporter.

Issue

During npm install for the angular_frontend the following error messages appear:

npm error code ETARGET
npm error notarget No matching version found for karma-coverage@~2.2.2.
npm error notarget In most cases you or one of your dependencies are requesting
npm error notarget a package version that doesn't exist.
npm error code ETARGET
npm error notarget No matching version found for karma-jasmine-html-reporter@~2.2.2.
npm error notarget In most cases you or one of your dependencies are requesting
npm error notarget a package version that doesn't exist.

This aborts the installation.

Origin

  • commit bab4d4a moved karma-jasmine-html-reporter from ~2.1.0 to ~2.1.1
  • commit e64a844 moved karma-jasmine-html-reporter from ~2.1.1 to ~2.2.0
  • commit 90f682d moved both from ~2.2.0 to ~2.2.1
  • commit 2a7085b moved both from ~2.2.1 to ~2.2.2

Thus both are now at ~2.2.2.

However, as of this date:

Running npm view <package> versions for both of these packages also results in these versions as their highest available.

Solution

Returning both packages to their corresponding highest available version.

  • ~2.2.1 for karma-coverage
  • ~2.1.0 for karma-jasmine-html-reporter

This solves the aforementioned error messages and makes fresh installations possible again.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions