Fix deprecation warnings while installing Nightwatch #4306
Comments
|
Heyy can i work on this issue could you please assign this to me ? |
|
@ansh7432 Sure, go ahead! |
|
Hey, |
|
I had raised the pr please check that |
|
Hello @garg3133 , could you please guide me because seems like mocha and archiver-utils uses older versions of glob which is transitive causing the issue . I think overriding glob :^9.0.0 only works locally but it won't work while publishing to npm , so is it possible to force them to use glob 9.0.0 or above in npm package ? |
|
@souravkv Older version of So, we would need to update the |
|
@garg3133 Ok , fixing |
|
@garg3133 should I open a issue in |
|
@souravkv You can. Also, feel free to raise a PR to update the version of |
|
A PR to bump the version of glob in mocha was just merged yesterday: mochajs/mocha#5250 |
|
@garg3133 ok I just raised a PR in |
Fix deprecation warnings while installing Nightwatch nightwatchjs#4306. 1. Update Node.js. 2.Update dependencies using --legacy-peer to ignore peer dependency conflicts and proceed with the installation anyway. 3.Update nightwatch to latest version. 4.Check issues with the node modules and package-lock.json. 5.Then , download the dependencies.
Description of the bug/issue
During the installation of Nightwatch using the
npm i -D nightwatchcommand, the following deprecation warnings are encountered:Steps to reproduce
Install Nightwatch in an existing Node project:
npm i -D nightwatch.To create a new Node project:
mkdir test-projectcd test-projectnpm initSample test
No response
Command to run
No response
Verbose Output
No response
Nightwatch Configuration
No response
Nightwatch.js Version
3.9.0
Node Version
No response
Browser
No response
Operating System
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: