crystalui / angular-lightbox

A simple, responsive lightbox component.
Apache License 2.0
21 stars 13 forks source link

npm update trouble #18

Open rissom opened 3 years ago

rissom commented 3 years ago

Lightbox seems to expect Angular 9.0.7. I use 11.2.7. If I use the --force option it works without problems. I am sorry, I don't have any experience in how to set up npm packages, but this seems to be some issue with the declaration of the dependencies. THANK YOU FOR THE GREAT PACKAGE!

(node:16980) ExperimentalWarning: The fs.promises API is experimental
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: frontend@0.0.1
npm ERR! Found: @angular/common@11.2.7
npm ERR! node_modules/@angular/common
npm ERR!   @angular/common@"^11.2.7" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^9.0.7" from @crystalui/angular-lightbox@1.1.8
npm ERR! node_modules/@crystalui/angular-lightbox
npm ERR!   @crystalui/angular-lightbox@"^1.1.8" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\thorsten.rissom\AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\thorsten.rissom\AppData\Local\npm-cache\_logs\2021-03-30T08_27_14_974Z-debug.log

the mentioned debug-file reads:

# npm resolution error report

2021-03-30T08:27:14.878Z

While resolving: frontend@0.0.1
Found: @angular/common@11.2.7
node_modules/@angular/common
  @angular/common@"^11.2.7" from the root project

Could not resolve dependency:
peer @angular/common@"^9.0.7" from @crystalui/angular-lightbox@1.1.8
node_modules/@crystalui/angular-lightbox
  @crystalui/angular-lightbox@"^1.1.8" from the root project

Fix the upstream dependency conflict, or retry
this command with --force, or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

Raw JSON explanation object:

{
  "code": "ERESOLVE",
  "current": {
    "name": "@angular/common",
    "version": "11.2.7",
    "whileInstalling": {
      "name": "frontend",
      "version": "0.0.1",
      "path": "C:\\www\\OXPV-BRB-DB\\frontend"
    },
    "location": "node_modules/@angular/common",
    "dependents": [
      {
        "type": "prod",
        "name": "@angular/common",
        "spec": "^11.2.7",
        "from": {
          "location": "C:\\www\\OXPV-BRB-DB\\frontend"
        }
      }
    ]
  },
  "edge": {
    "type": "peer",
    "name": "@angular/common",
    "spec": "^9.0.7",
    "error": "INVALID",
    "from": {
      "name": "@crystalui/angular-lightbox",
      "version": "1.1.8",
      "whileInstalling": {
        "name": "frontend",
        "version": "0.0.1",
        "path": "C:\\www\\OXPV-BRB-DB\\frontend"
      },
      "location": "node_modules/@crystalui/angular-lightbox",
      "dependents": [
        {
          "type": "prod",
          "name": "@crystalui/angular-lightbox",
          "spec": "^1.1.8",
          "from": {
            "location": "C:\\www\\OXPV-BRB-DB\\frontend"
          }
        }
      ]
    }
  },
  "peerConflict": null,
  "strictPeerDeps": false,
  "force": false
}
orcunozbay commented 1 year ago

I guess forgotten repository.

webcluesgit commented 1 month ago

Same issue. Any update??

image