Having issue with chromedriver installation not actually installing new version of driver...

[ColeTown]

So I have a dependency that uses chromedriver, but the version that was installed with that only supports up to v88. I tried to remedy this by installing chromedriver myself and the package-lock.json reflects this change and shows 98.0.1 as well as the package.json. However, whenever I run my dependencies module that uses chromedriver I get the following SessionNotCreatedError:

SessionNotCreatedError: session not created: This version of ChromeDriver only supports Chrome version 88
Current browser version is 98.0.4758.102 with binary path C:\Program Files\Google\Chrome\Application\chrome.exe
  (Driver info: chromedriver=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}),platform=Windows NT 10.0.19043 x86_64)
    at Object.checkLegacyResponse (C:\Users\c4tow\PersonalProject\node_modules\pepper-mint\node_modules\selenium-webdriver\lib\error.js:546:15)
    at parseHttpResponse (C:\Users\c4tow\PersonalProject\node_modules\pepper-mint\node_modules\selenium-webdriver\lib\http.js:509:13)
    at C:\Users\c4tow\PersonalProject\node_modules\pepper-mint\node_modules\selenium-webdriver\lib\http.js:441:30
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
From: Task: WebDriver.createSession()
    at Function.createSession (C:\Users\c4tow\PersonalProject\node_modules\pepper-mint\node_modules\selenium-webdriver\lib\webdriver.js:769:24)
    at Function.createSession (C:\Users\c4tow\PersonalProject\node_modules\pepper-mint\node_modules\selenium-webdriver\chrome.js:761:15)
    at createDriver (C:\Users\c4tow\PersonalProject\node_modules\pepper-mint\node_modules\selenium-webdriver\index.js:170:33)
    at Builder.build (C:\Users\c4tow\PersonalProject\node_modules\pepper-mint\node_modules\selenium-webdriver\index.js:642:16)
    at ChromedriverMintAuth.<anonymous> (C:\Users\c4tow\PersonalProject\node_modules\pepper-mint\dist\auth\chromedriver-auth.js:68:18)
    at Generator.next (<anonymous>)
    at C:\Users\c4tow\PersonalProject\node_modules\pepper-mint\dist\auth\chromedriver-auth.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (C:\Users\c4tow\PersonalProject\node_modules\pepper-mint\dist\auth\chromedriver-auth.js:4:12)
    at ChromedriverMintAuth.createDriver (C:\Users\c4tow\PersonalProject\node_modules\pepper-mint\dist\auth\chromedriver-auth.js:65:16) {
  remoteStacktrace: ''
}

So apparently, the newest version of chromedriver isn't actually installed... even though my package-lock.json says it is.
I've tried multiple times to update the chromedriver in different ways, but still no luck.
Is this just a fluke? Is there anything on the side of this module that could cause this or could this be caused by the module using it?

[ColeTown]

Nevermind... I figured it out. It is the way modules work in dependencies that got me. For people who want to know, I was updating chrome driver in my node_module folder, and not the dependencies node_module folder. Had to cd into the dependency and run npm update again and it worked right away.

Am new to node.js so sorry about that.