Closed reallymello closed 1 year ago
After trying lots of troubleshooting steps to further distill the cause I can't get it to happen anymore
I tried this as well on Windows 10 Enterprise with both Git Bash and the basic CMD terminals and seems alright.
I'll close it for now and will reopen if it comes back with a sequence I can isolate
Description of the bug/issue
When I run a test I expect to see the Nightwatch test execution output, but instead I see console log statements that appear to be a test of the
@colors/colors
package@colors\colors\examples\normal-usage.js
that gets added as an internal dependency when isntalling Nightwatch 2.6.3.Steps to reproduce
Windows 10
mkdir exampleFolder
cd exampleFolder
npm install nightwatch@latest
npx nightwatch
nightwatch.conf.js
src_folders
to./test
npx nightwatch
You get this weird output that seems to match console.log statements in node_modules\@colors\colors\examples\normal-usage.js.
Also, I don't think the test itself runs. The browser never launches and I never see any Nightwatch commands executed.
Sample test
Command to run
Verbose Output
No response
Nightwatch Configuration
Nightwatch.js Version
2.6.3
Node Version
16.15.0
Browser
Chrome 108
Operating System
Windows 10
Additional Information
The file that seems to be logging this is in @colors\colors\examples\normal-usage.js
package-lock.json has a couple references to it