"Unable to resolve dependency tree" error during NPM install of APM-Start #143

jedibob5 · 2021-01-05T18:26:00Z

I am using the Angular: Getting Started Pluralsight lesson and I am attempting to run npm install on the APM-Start folder found in the repository. I am receiving this error message, not entirely sure what it means but I think it might indicate a mismatched version somewhere? I have some experience with npm in the past, though I've never been good at troubleshooting it.

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/compiler
npm ERR!   @angular/compiler@"~10.0.4" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/compiler@"10.2.4" from @angular/[email protected]
npm ERR! node_modules/@angular/compiler-cli
npm ERR!   peer @angular/compiler-cli@">=10.0.0-next.0 < 11" from @angular-devkit/[email protected]
npm ERR!   node_modules/@angular-devkit/build-angular
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 /Users/robert.anderson/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/robert.anderson/.npm/_logs/2021-01-05T18_17_06_138Z-debug.log

How would I resolve this issue?

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

DeborahK · 2021-01-05T21:31:36Z

Did you see any errors after running npm install?

Did you run npm audit fix? Running the fix will cause a mismatch with your versions, so it should not be run.

Try this:

Delete node_module folder and the package-lock.json file.
Run npm cache verify to verify and clean up your npm.
Run npm install again. (Do NOT run npm audit fix)
Run npm start

Let me know if that resolves the issue.

jedibob5 · 2021-01-05T21:41:57Z

The error I posted is the error that occurs when I attempt to run npm install. It doesn't appear that a package-lock or node_modules folder even got generated in the project folder. I have not run npm audit fix at any point.

I decided to run npm cache verify anyway to see what happened, this was the output.

robert.anderson@ATGs-MBP APM-Start % npm cache verify
Cache verified and compressed (~/.npm/_cacache)
Content verified: 1525 (84613636 bytes)
Content garbage-collected: 1 (987145 bytes)
Index entries: 1525
Finished in 4.157s

npm install still fails with the same error after running this.

DeborahK · 2021-01-05T22:33:41Z

I haven't seen that error before.

Had you done anything else? Or installed anything else into that folder?

What version of node and npm do you have?

Reading this: https://stackoverflow.com/questions/64573177/unable-to-resolve-dependency-tree-error-when-installing-npm-packages

Suggests trying:

npm install --force
npm install --legacy-peer-deps

But I don't know why you would suddenly see this. The dependencies in the package.json file should all be compatible unless something else was installed to modify it.

EDIT:
If you want to continue with the course without having to install anything, try using stackblitz as per the instructions here: https://github.com/DeborahK/Angular-GettingStarted#stackblitz

jedibob5 · 2021-01-06T14:17:38Z

I talked to a coworker who was also taking the course and was encountering the same issue. He had figured out that updating the Angular dependencies to the latest 10.x release (~10.2.4 for most @angular dependencies, @angular/cli on ~10.2.1) resolved the problem, and npm install now runs successfully.

I could make a PR with the package.json updates, though if it's not reproducible on machines other than the two of ours it's probably worth investigating more before applying a fix. Versions of potentially relevant things below:

OS: Mac OSX Big Sur 11.1
node -v: v15.5.1
npm -v: 7.3.0
nvm -v: 0.37.2

Let me know if there's any other information I could provide that might help.

DeborahK · 2021-01-06T16:52:43Z

Thank you for the additional information. I'll spend some more time on it today, trying it on several machines, and I'll update the code as needed.

mnaeem76 · 2021-01-12T11:28:46Z

@DeborahK I'm having similar problem. I have the following Specs:

OS: Windows 10
node -v: v15.5.1
npm: 7.3.0

I also ran npm cache verify

Cache verified and compressed (~\AppData\Local\npm-cache\_cacache)
Content verified: 3469 (151630332 bytes)
Content garbage-collected: 25 (28857697 bytes)
Index entries: 3469
Finished in 28.403s

When I ran npm install on the source code downloaded from GitHub (which targets angular 10) I got these errors

# npm resolution error report

2021-01-12T11:13:11.681Z

While resolving: [email protected]
Found: @angular/[email protected]
node_modules/@angular/compiler
  @angular/compiler@"~10.0.4" from the root project

Could not resolve dependency:
peer @angular/compiler@"10.2.4" from @angular/[email protected]
node_modules/@angular/compiler-cli
  peer @angular/compiler-cli@">=10.0.0-next.0 < 11" from @angular-devkit/[email protected]
  node_modules/@angular-devkit/build-angular

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/compiler",
    "version": "10.0.14",
    "whileInstalling": {
      "name": "apm",
      "version": "0.0.0",
      "path": "D:\\Learning\\Angular\\Pluralsight\\Getting Started\\10\\APM"
    },
    "location": "node_modules/@angular/compiler",
    "dependents": [
      {
        "type": "prod",
        "name": "@angular/compiler",
        "spec": "~10.0.4",
        "from": {
          "location": "D:\\Learning\\Angular\\Pluralsight\\Getting Started\\10\\APM"
        }
      }
    ]
  },
  "edge": {
    "type": "peer",
    "name": "@angular/compiler",
    "spec": "10.2.4",
    "error": "INVALID",
    "from": {
      "name": "@angular/compiler-cli",
      "version": "10.2.4",
      "whileInstalling": {
        "name": "apm",
        "version": "0.0.0",
        "path": "D:\\Learning\\Angular\\Pluralsight\\Getting Started\\10\\APM"
      },
      "location": "node_modules/@angular/compiler-cli",
      "dependents": [
        {
          "type": "peer",
          "name": "@angular/compiler-cli",
          "spec": ">=10.0.0-next.0 < 11",
          "from": {
            "name": "@angular-devkit/build-angular",
            "version": "0.1000.8",
            "whileInstalling": {
              "name": "apm",
              "version": "0.0.0",
              "path": "D:\\Learning\\Angular\\Pluralsight\\Getting Started\\10\\APM"
            },
            "location": "node_modules/@angular-devkit/build-angular",
            "dependents": []
          }
        }
      ]
    }
  },
  "peerConflict": null,
  "strictPeerDeps": false,
  "force": false
}

The exercise files from Pluralsight (which target angualr 9) seem to compile just fine. I simply copied the contentsof the packages.json file from exercise folder on to packages.json file from GitHub, and I was able to compile without issues.

Not sure what is happening since I'm a newbie to all this. If you can help me figure out what I should do, that will be great. Perhaps I can continue the course with angular 9 from the exercise files? Or you think I should pursue the angular 10 track if that's going to affect the learning process.

I'm attaching here a zip file with 2 packages.json files for your reference; one taken originally from GitHub APM-start and other from Exercises on Pluralsight
Packages files.zip

Thanks,
Mudasser

mnaeem76 · 2021-01-12T12:16:13Z

@DeborahK Just wanted to update you that I was able to compile successfully with GitHub APM-Start version (that uses angular 10). I realized I had installed latest version of node.js instead of the LTS. I uninstalled node.js and installed again, this time using LTS.

My current versions are:

node:  v14.15.4
npm: 6.14.10

Since I'm a newbie, I think I'll just focus on learning via the course outline and lectures rather than diving into unchartered territory!

Thanks
Mudasser

DeborahK · 2021-01-12T16:51:24Z

Hi @mnaeem76 Sounds like you were able to move forward. Let me know if you have any further questions.

And thank you for letting me know that the exercise files were not updated to Angular v10.

Spring3 · 2021-03-13T22:57:42Z

Got this error in my personal repo

It looks like it happened to me due to the new version of lock file which was not supported by a lower version of npm.

I also got the following message:

npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!

deleting the node_modules and re-generating lock file helped in my case.

himanshigupta29 · 2021-04-09T13:29:31Z

it is because of a compatibility issue between npm and ng

flutterq · 2021-05-11T15:34:34Z

[Solved] Unable to resolve dependency tree error for creating new angular project

alundiak · 2021-06-13T14:45:15Z

Just in case, I did have similar behavior, when I tried either npm upgrade my current Angular 11.x based boilerplate from previous ng new or create new ng new abc based on Angular 12.x. I simply forgot to upgrade Angular CLI. So this npm install -g @angular/cli@latest solved my errors during ng new abc.

bkiprono · 2021-08-27T08:02:47Z

I'm undergoing the same.
Did you guys get a fix?

DeborahK · 2021-08-27T16:10:55Z

The first thing to check is to ensure you are using the "LTS" version of node, NOT the "current" version of node.

Then try this:

Delete node_module folder and the package-lock.json file.
Run npm cache verify to verify and clean up your npm.
Run npm install again. (Do NOT run npm audit fix)
Run npm start

Let me know if that resolves your issue.

davinma · 2021-09-10T08:36:55Z

Sometimes you should be downgrade your npm version, run nvm list and nvm use <version string here> first, then run npm install, and that worked for me.

HjoshM · 2021-09-11T14:16:29Z

After upgrading to the latest Angular cli, when I run ng serve, I get the following error:

./node_modules/@angular-devkit/build-angular/src/webpack/es5-polyfills.js:106:0-37 - Error: Module not found: Error: Can't resolve 'zone.js/plugins/zone-legacy' in 'C:\Users\Joshua\App\node_modules@angular-devkit\build-angular\src\webpack'

I have tried every solution and suggestion in the posts that exist about zone.js related issues and errors, including the solutions mentioned on this page, but nothing has resolved it...

Does anyone know how to fix this in the latest Angular version?

bvedant · 2021-10-01T21:54:44Z

After upgrading to the latest Angular cli, when I run ng serve, I get the following error:

./node_modules/@angular-devkit/build-angular/src/webpack/es5-polyfills.js:106:0-37 - Error: Module not found: Error: Can't resolve 'zone.js/plugins/zone-legacy' in 'C:\Users\Joshua\App\node_modules@angular-devkit\build-angular\src\webpack'

I have tried every solution and suggestion in the posts that exist about zone.js related issues and errors, including the solutions mentioned on this page, but nothing has resolved it...

Does anyone know how to fix this in the latest Angular version?

Running into the exact same issue as you.

DeborahK · 2021-10-01T22:10:21Z

What version of the Angular CLI are you using? When you updated the Angular CLI version, did you update the version of the Angular libraries in the project as well? (The locally installed version of the Angular CLI should match with its associated version of the Angular libraries in the project.)

What happens if you delete your package-lock.json file and your node-modules folder and you re-run npm install again?

bvedant · 2021-10-01T22:19:03Z

What version of the Angular CLI are you using? When you updated the Angular CLI version, did you update the version of the Angular libraries in the project as well? (The locally installed version of the Angular CLI should match with its associated version of the Angular libraries in the project.)

What happens if you delete your package-lock.json file and your node-modules folder and you re-run npm install again?

Hi Deborah, actually I was able to fix the issue and I landed on this page from someone else's tutorial that was giving me the same error as HJosh had, but what I did to fix my environemnt was copy package.json dependency sections with up-to-date values, deleting node_modules/ and pakcage-lock.json, and running npm install with the --legacy-peer-deps flag.

amit-jadhav · 2021-11-26T13:20:29Z

I tried all the solutions provided on this page. None of them worked for me. I am using npm version 8.1.0.

ERROR:
`npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/common
npm ERR! @angular/common@"~8.2.8" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^9.0.0" from [email protected]
npm ERR! node_modules/ag-grid-angular
npm ERR! ag-grid-angular@"^23.2.1" 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\xxx\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\xxx\AppData\Local\npm-cache_logs\2021-11-26T12_22_55_659Z-debug.log`

When I tried to use --force, or --legacy-peer-deps option the command executes forever (command doesn't return any result).

Please provide some solution to this issue.

DeborahK · 2021-11-26T17:57:10Z

@amit-jadhav This github repo contains the code for my Angular: Getting Started course. It doesn't look like the code you are compiling is from this course.

If you have a more general Angular question, please post to stackoverflow.com.

That said, reading your error message, it sounds like your Angular project is v8, but your ag-grid is looking for Angular v9. It's important to ensure you have appropriate versions of third party components that match the version of Angular you have. (Angular is now on v13)

Hope you can resolve your issue.

cabbad · 2021-12-02T02:28:34Z

我的是node版本太高了，重新安装对应版本就行

ghost · 2021-12-08T07:40:18Z

I want to see you.
[email protected]

vinishgeorge · 2022-02-18T05:59:29Z

node version : lts/gallium -> v16.14.0
ng new auth0-poc
Fails while creating the project with error
? Would you like to add Angular routing? Yes
? Which stylesheet format would you like to use? SCSS [ https://sass-lang.com/documentation/syntax#scss ]
CREATE auth0-poc/README.md (1025 bytes)
CREATE auth0-poc/.editorconfig (246 bytes)
CREATE auth0-poc/.gitignore (631 bytes)
CREATE auth0-poc/angular.json (3679 bytes)
CREATE auth0-poc/package.json (1286 bytes)
CREATE auth0-poc/tsconfig.json (489 bytes)
CREATE auth0-poc/tslint.json (1953 bytes)
CREATE auth0-poc/browserslist (429 bytes)
CREATE auth0-poc/karma.conf.js (1021 bytes)
CREATE auth0-poc/tsconfig.app.json (210 bytes)
CREATE auth0-poc/tsconfig.spec.json (270 bytes)
CREATE auth0-poc/src/favicon.ico (948 bytes)
CREATE auth0-poc/src/index.html (294 bytes)
CREATE auth0-poc/src/main.ts (372 bytes)
CREATE auth0-poc/src/polyfills.ts (2835 bytes)
CREATE auth0-poc/src/styles.scss (80 bytes)
CREATE auth0-poc/src/test.ts (753 bytes)
CREATE auth0-poc/src/assets/.gitkeep (0 bytes)
CREATE auth0-poc/src/environments/environment.prod.ts (51 bytes)
CREATE auth0-poc/src/environments/environment.ts (662 bytes)
CREATE auth0-poc/src/app/app-routing.module.ts (246 bytes)
CREATE auth0-poc/src/app/app.module.ts (393 bytes)
CREATE auth0-poc/src/app/app.component.scss (0 bytes)
CREATE auth0-poc/src/app/app.component.html (25755 bytes)
CREATE auth0-poc/src/app/app.component.spec.ts (1068 bytes)
CREATE auth0-poc/src/app/app.component.ts (214 bytes)
CREATE auth0-poc/e2e/protractor.conf.js (808 bytes)
CREATE auth0-poc/e2e/tsconfig.json (214 bytes)
CREATE auth0-poc/e2e/src/app.e2e-spec.ts (642 bytes)
CREATE auth0-poc/e2e/src/app.po.ts (301 bytes)
⠏ Installing packages...npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/jasmine-core
npm ERR! dev jasmine-core@"~3.5.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer jasmine-core@">=3.8" from [email protected]
npm ERR! node_modules/karma-jasmine-html-reporter
npm ERR! dev karma-jasmine-html-reporter@"^1.4.2" 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 /home/vg/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/vg/.npm/_logs/2022-02-18T05_46_05_464Z-debug-0.log
✖ Package install failed, see above.

node version : lts/fermium -> v14.19.0
ng new auth0-poc

Works fine without error.

DeborahK · 2022-02-18T07:48:29Z

This issue seems better posted to the Angular/CLI repo so the team responsible for the CLI can help.

israeladam · 2022-03-15T23:49:19Z

Having the same issue when trying to add bootstrap

npm ERR! code ERESOLVE                             
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/compiler@"13.2.6" from @angular/[email protected]
npm ERR! node_modules/@angular/localize
npm ERR!   peer @angular/localize@"^13.0.0" from @ng-bootstrap/[email protected]
npm ERR!   node_modules/@ng-bootstrap/ng-bootstrap
npm ERR!     @ng-bootstrap/ng-bootstrap@"12.0.0" 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\Adnan\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\Adnan\AppData\Local\npm-cache\_logs\2022-03-15T23_45_41_407Z-debug-0.log
× Package install failed, see above.

Angular CLI: 13.0.4
Node: 16.14.0
Package Manager: npm 8.3.1
OS: win32 x64

DeborahK · 2022-03-16T05:30:56Z

The course uses bootstrap, not ng-bootstrap. Which were you trying to install?

…gStarted#143

panksahu · 2023-01-13T03:47:10Z

Hello,
I am facing looks like similar issue. Tried whole night by manually adding in package.json for peerDependencies, but didn't got any clue for the correct fix...on local i ma able to run it by execute command.

1-Delete node_module folder and the package-lock.json file.
2-Run npm cache verify to verify and clean up your npm.
3-npm install --legacy-peer-deps

stack: Error: Command failed: npm install
npm WARN config global --global, --local are deprecated. Use --location=global instead.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @microsoft/[email protected]
npm ERR! node_modules/@microsoft/teams-js
npm ERR! @microsoft/teams-js@"^2.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @microsoft/teams-js@"^1.8.0" from [email protected]
npm ERR! node_modules/msteams-react-base-component
npm ERR! msteams-react-base-component@"^3.1.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @microsoft/[email protected]
npm ERR! node_modules/@microsoft/teams-js
npm ERR! peer @microsoft/teams-js@"^1.8.0" from [email protected]
npm ERR! node_modules/msteams-react-base-component
npm ERR! msteams-react-base-component@"^3.1.0" 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.

My package json is:

panksahu · 2023-01-13T03:48:06Z

This is not working and throwing above error while direct deploying on azure from VS code.

vinay-kumar-uppala · 2023-03-17T15:19:01Z

I haven't seen that error before.

Had you done anything else? Or installed anything else into that folder?

What version of node and npm do you have?

Reading this: https://stackoverflow.com/questions/64573177/unable-to-resolve-dependency-tree-error-when-installing-npm-packages

Suggests trying:

npm install --force

npm install --legacy-peer-deps

But I don't know why you would suddenly see this. The dependencies in the package.json file should all be compatible unless something else was installed to modify it.

EDIT: If you want to continue with the course without having to install anything, try using stack blitz as per the instructions here: https://github.com/DeborahK/Angular-GettingStarted#stackblitz

I have tried this one, and it's working fine without any errors.
Thanks!!

RaminMoghtader · 2023-08-22T20:15:08Z

@DeborahK Dear Ms. Kurata. Thank you for all the great information and the courses. I appreciate your style of teaching and your courses very much.

Looks like I also ran into the same issue as the rest of the comments here, which apparantly have to do with Node Versions and Ng version. Based on information provided from @mnaeem76 ( thanks)
node: v14.15.4
npm: 6.14.10
I've used now NVM to install the required version and am running Dem-Start.

My Question: What are the enhanced and added changes we need to learn to augment the Reactive Forms course that you have provided? Thanks again for a great course and information

RM

manikiran949 · 2025-02-03T08:52:16Z

I encountered a similar error in React, and running ,
npm config set legacy-peer-deps true resolved it for me .

DeborahK closed this as completed Jan 12, 2021

ghost mentioned this issue May 12, 2021

v2.0.0-beta.1 - fails to npm install command jhipster/generator-jhipster-nodejs#227

Closed

allizwarttech added a commit to iballi2017/TEP-Digital-LRP-angular-frontend that referenced this issue Aug 10, 2022

new package-lock.json file to resolve errors: DeborahK/Angular-Gettin…

e9c512c

…gStarted#143

allizwarttech added a commit to iballi2017/TEP-Digital-LRP-angular-frontend that referenced this issue Aug 10, 2022

new package-lock.json file to resolve errors: DeborahK/Angular-Gettin…

7cc7cf8

…gStarted#143

jeyadheesh-clustrex mentioned this issue Feb 10, 2025

Bug: "npm install" fails with ERESOLVE unable to resolve dependency tree jeyadheesh-clustrex/n8n_test#4

Open

"Unable to resolve dependency tree" error during NPM install of APM-Start #143

"Unable to resolve dependency tree" error during NPM install of APM-Start #143

Comments

jedibob5 commented Jan 5, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

DeborahK commented Jan 5, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jedibob5 commented Jan 5, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

DeborahK commented Jan 5, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jedibob5 commented Jan 6, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

DeborahK commented Jan 6, 2021

Uh oh!

mnaeem76 commented Jan 12, 2021

Uh oh!

mnaeem76 commented Jan 12, 2021

Uh oh!

DeborahK commented Jan 12, 2021

Uh oh!

Spring3 commented Mar 13, 2021

Uh oh!

himanshigupta29 commented Apr 9, 2021

Uh oh!

flutterq commented May 11, 2021

Uh oh!

alundiak commented Jun 13, 2021

Uh oh!

bkiprono commented Aug 27, 2021

Uh oh!

DeborahK commented Aug 27, 2021

Uh oh!

davinma commented Sep 10, 2021

Uh oh!

HjoshM commented Sep 11, 2021

Uh oh!

bvedant commented Oct 1, 2021

Uh oh!

DeborahK commented Oct 1, 2021

Uh oh!

bvedant commented Oct 1, 2021

Uh oh!

amit-jadhav commented Nov 26, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

DeborahK commented Nov 26, 2021

Uh oh!

cabbad commented Dec 2, 2021

Uh oh!

ghost commented Dec 8, 2021

Uh oh!

vinishgeorge commented Feb 18, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

DeborahK commented Feb 18, 2022

Uh oh!

israeladam commented Mar 15, 2022

Uh oh!

DeborahK commented Mar 16, 2022

Uh oh!

panksahu commented Jan 13, 2023

Uh oh!

panksahu commented Jan 13, 2023

Uh oh!

vinay-kumar-uppala commented Mar 17, 2023

Uh oh!

RaminMoghtader commented Aug 22, 2023

Uh oh!

manikiran949 commented Feb 3, 2025

Uh oh!

jedibob5 commented Jan 5, 2021 •

edited

Loading

DeborahK commented Jan 5, 2021 •

edited

Loading

jedibob5 commented Jan 5, 2021 •

edited

Loading

DeborahK commented Jan 5, 2021 •

edited

Loading

jedibob5 commented Jan 6, 2021 •

edited

Loading

amit-jadhav commented Nov 26, 2021 •

edited

Loading

vinishgeorge commented Feb 18, 2022 •

edited

Loading