I am using webdriver-manager 12.0.6 both globally and within my local project.
When I run webdriver-manager update--standalone false locally I get unhandled promise rejection errors:
$ node_modules/.bin/webdriver-manager update --standalone false
webdriver-manager: using local installed version 12.0.6
(node:13792) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: ENOENT: no such file or directory, open 'C:\Users\<MY_USERNAME>\src\<MY_PROJECT>\api\ClientApp\node_modules\webdriver-manager\selenium\chrome-response.xml'
(node:13792) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:13792) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: ENOENT: no such file or directory, open 'C:\Users\<MY_USERNAME>\src\<MY_PROJECT>\api\ClientApp\node_modules\webdriver-manager\selenium\gecko-response.json'
When I run the same command globally everything works without issue.
$ webdriver-manager clean
[12:49:15] I/file_manager - removed chromedriver_2.37.exe
[12:49:15] I/file_manager - removed chromedriver_2.37.zip
[12:49:15] I/file_manager - removed geckodriver-v0.20.0.exe
[12:49:15] I/file_manager - removed geckodriver-v0.20.0.zip
[12:49:15] I/file_manager - removed gecko-response.json
[12:49:15] I/file_manager - removed standalone-response.xml
$ webdriver-manager update --standalone false
[12:49:24] I/update - chromedriver: unzipping chromedriver_2.37.zip
[12:49:25] I/update - geckodriver: unzipping geckodriver-v0.20.0.zip
I have tried deleting node_modules and rerunning yarn. Not sure what else is at play here. What steps can I take to further troubleshoot this?
Delete the folder:
C:\Users\<MY_USERNAME>\src\<MY_PROJECT>\api\ClientApp\node_modules\webdriver-manager\selenium
Run the webdriver-manager update --standalone false again in new opened cmd window
Related
My gatsby website was running locally without problems and when I tried to restart it today without updating the code, the npm run develop build succeeds. However, when I try to open localhost in browser, this error is thrown in the terminal:
success Building development bundle - 16.014s
success Writing page-data.json files to public directory - 0.103s - 3/11
106.93/s
(node:2043) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'split' of undefined
at parseError (/Users/sp/Documents/jamstack/training/frontend/node_modules/gatsby/src/utils/dev-ssr/render-dev-html-child.js:52:26)
at /Users/sp/Documents/jamstack/training/frontend/node_modules/gatsby/src/utils/dev-ssr/render-dev-html-child.js:106:27
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:2043) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejeæction, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:2043) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
I can't seem to work out where this error is coming from as I did not change any of the code that was working earlier.
Does anyone have an idea?
There's no detail about the running version of Gatsby but according to this GitHub thread, while the issue is being fixed in the next release you can bypass it by installing a canary version:
npm i gatsby#webpack-split-fix
I am trying to run command npm run build. I am getting error
`make i info Invoking build target
make i info Invoking dist/build target
(node:15892) UnhandledPromiseRejectionWarning: undefined
(Use `node --trace-warnings ...` to show where the warning was created)
(node:15892) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:15892) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
make × ERR not found: make-$(SOURCE_FILES)`
Please anyone can help me to solve the problem.
I finally solved it installing make command using chocolaty in my window. I was getting error because make was not installed on my windows (I had no idea regarding that make is window's command not NodeJs').
This post helped me to solve my problem.
How to install and use "make" in Windows?
When I try to download ie driver for protractor testing, I do
webdriver-manager update --ie
but I get the below error
(node:17636) UnhandledPromiseRejectionWarning: TypeError: Invalid Version: .3.150.2
at new SemVer (C:\Users\francisp\AppData\Roaming\npm\node_modules\protractor\node_modules\semver\semver.js:323:11)
at compare (C:\Users\francisp\AppData\Roaming\npm\node_modules\protractor\node_modules\semver\semver.js:614:10)
at Function.gt (C:\Users\francisp\AppData\Roaming\npm\node_modules\protractor\node_modules\semver\semver.js:643:10)
at C:\Users\francisp\AppData\Roaming\npm\node_modules\protractor\node_modules\webdriver-manager\built\lib\binaries\iedriver_xml.js:43:33
(Use `node --trace-warnings ...` to show where the warning was created)
(node:17636) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:17636) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[21:41:10] I/update - selenium standalone: file exists C:\Users\francisp\AppData\Roaming\npm\node_modules\protractor\node_modules\webdriver-manager\selenium\selenium-server-standalone-3.141.59.jar
[21:41:10] I/update - selenium standalone: selenium-server-standalone-3.141.59.jar up to date
[21:41:10] I/update - chromedriver: file exists C:\Users\francisp\AppData\Roaming\npm\node_modules\protractor\node_modules\webdriver-manager\selenium\chromedriver_94.0.4606.61.zip
[21:41:10] I/update - chromedriver: unzipping chromedriver_94.0.4606.61.zip
[21:41:10] I/update - chromedriver: chromedriver_94.0.4606.61.exe up to date
[21:41:10] I/update - geckodriver: file exists C:\Users\francisp\AppData\Roaming\npm\node_modules\protractor\node_modules\webdriver-manager\selenium\geckodriver-v0.30.0.zip
[21:41:10] I/update - geckodriver: unzipping geckodriver-v0.30.0.zip
[21:41:10] I/update - geckodriver: geckodriver-v0.30.0.exe up to date
Can somebody help please? TIA
Tried this below and it worked.
webdriver-manager update --ie --versions.ie=3.9.0
instead of
webdriver-manager update --ie
Also while starting the server, you have to use
webdriver-manager start --ie --versions.ie=3.9.0
instead of
webdriver-manager start
I'm trying:
vue-native init test-project
And I'm getting this output:
Using globally installed expo-cli 3.0.10
Creating Vue Native project project-new
Creating project with expo-cli
[09:09:29] --name: argument is required in non-interactive mode. √
Created project with expo-cli
(node:9072) UnhandledPromiseRejectionWarning: Error: ENOENT: no such
file or directory, chdir 'project-new'
at process.chdir (internal/process/main_thread_only.js:31:12)
at installPackages (C:\Users\User\AppData\Roaming\npm\node_modules\vue-native-cli\src\index.js:182:11)
at createExpoProject (C:\Users\User\AppData\Roaming\npm\node_modules\vue-native-cli\src\index.js:123:3)
at init (C:\Users\User\AppData\Roaming\npm\node_modules\vue-native-cli\src\index.js:101:5)
at Command. (C:\Users\User\AppData\Roaming\npm\node_modules\vue-native-cli\src\index.js:69:7)
at Command.listener (C:\Users\User\AppData\Roaming\npm\node_modules\vue-native-cli\node_modules\commander\index.js:315:8)
at Command.emit (events.js:182:13)
at Command.parseArgs (C:\Users\User\AppData\Roaming\npm\node_modules\vue-native-cli\node_modules\commander\index.js:651:12)
at Command.parse (C:\Users\User\AppData\Roaming\npm\node_modules\vue-native-cli\node_modules\commander\index.js:474:21)
at Object. (C:\Users\User\AppData\Roaming\npm\node_modules\vue-native-cli\src\index.js:81:9)
(node:9072) UnhandledPromiseRejectionWarning: Unhandled promise
rejection. This error originated either by throwing inside of an async
function without a catch block, or by rejecting a promise which was
not handled with .catch(). (rejection id: 1) (node:9072) [DEP0018]
DeprecationWarning: Unhandled promise rejections are deprecated. In
the future, promise rejections that are not handled will terminate the
Node.js process with a non-zero exit code.
I've already installed React Native CLI, Expo CLI, and Vue Native CLI. I tried to solve the issue by updating npm but it did not work.
Also when I run:
vue-native init test-project --no-crna
it is ok and no errors appear.
I have a react-native project When I start react-native run-android on windows 10 environment it's working but I worked react-native run-ios MacOS environment my bundle terminal gives this error,
Loading dependency graph...(node:46534) UnhandledPromiseRejectionWarning: Error: jest-haste-map: Haste module naming collision:
Duplicate module name: react-native
Paths: /Users/tanfener/Desktop/MPP/mpp/node_modules/react-native/package.json collides with /Users/tanfener/Desktop/MPP/mpp/ios/Pods/React/package.json
This error is caused by `hasteImpl` returning the same name for different files.
at setModule (/Users/tanfener/Desktop/MPP/mpp/node_modules/metro/node_modules/jest-haste-map/build/index.js:569:17)
at workerReply (/Users/tanfener/Desktop/MPP/mpp/node_modules/metro/node_modules/jest-haste-map/build/index.js:641:9)
at processTicksAndRejections (internal/process/task_queues.js:86:5)
(node:46534) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:46534) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:46534) UnhandledPromiseRejectionWarning: Error: jest-haste-map: Haste module naming collision:
Duplicate module name: react-native
Paths: /Users/tanfener/Desktop/MPP/mpp/node_modules/react-native/package.json collides with /Users/tanfener/Desktop/MPP/mpp/ios/Pods/React/package.json
This error is caused by `hasteImpl` returning the same name for different files.
at setModule (/Users/tanfener/Desktop/MPP/mpp/node_modules/metro/node_modules/jest-haste-map/build/index.js:569:17)
at workerReply (/Users/tanfener/Desktop/MPP/mpp/node_modules/metro/node_modules/jest-haste-map/build/index.js:641:9)
at processTicksAndRejections (internal/process/task_queues.js:86:5)
(node:46534) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3)
I tried
delete all node_modules
clear npm cache
delete watchman
I create new project its work but it's not working on my project
my package.json like that
https://ybin.me/p/8941c752fb540ea5#AxqA/1Ckte5N2k8crVggkmQGiRQjP5VOAF/TIxRo4Dw=
Podfile
# Uncomment the next line to define a global platform for your project
platform :ios, '9.0'
target 'mpp' do
# Uncomment the next line if you're using Swift or would like to use dynamic frameworks
# use_frameworks!
pod 'RNVectorIcons', :path => '../node_modules/react-native-vector-icons'
pod 'RNI18n', :path => '../node_modules/react-native-i18n'
# Pods for mpp
target 'mppTests' do
inherit! :search_paths
# Pods for testing
end
end
I had a same issue and below command help to solve it.
rm -rf ./node_modules && npm install
npm cache clean
npm start -- --reset-cache