EBUSY: resource busy or locked, rmdir - webdriver-io

I'm trying webdriverIO recently and got stuck at generating configuration file.
? Where should your tests be launched local - https://www.npmjs.com/package/#wdio/local-runner
? Shall I install the runner plugin for you? Yes
? Where is your automation backend located? On my local machine
? Which framework do you want to use? mocha
? Shall I install the framework adapter for you? Yes
? Do you want to run WebdriverIO commands synchronous or asynchronous? sync
? Where are your test specs located? ./test/specs/**/*.js
? Which reporter do you want to use? dot - https://www.npmjs.com/package/#wdio/dot-reporter
? Shall I install the reporter library for you? Yes
? Do you want to add a service to your test setup? (Press <space> to select, <a> to toggle all, <i> to invert selection)
? Level of logging verbosity trace
? What is the base url? http://localhost
Above is my configuration and I got following error:
Installing wdio packages:
- #wdio/local-runner
- #wdio/mocha-framework
- #wdio/dot-reporter
- #wdio/sync
yarn add v1.13.0
info No lockfile found.
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents#1.2.7: The platform "win32" is incompatible with this module.
info "fsevents#1.2.7" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning " > #wdio/mocha-framework#5.6.0" has unmet peer dependency "webdriverio#^5.0.0".
error An unexpected error occurred: "EBUSY: resource busy or locked, rmdir 'C:\\Users\\QualIT-AKL\\Desktop\\111\\node_modules\\.bin'".
info If you think this is a bug, please open a bug report with the information provided in "C:\\Users\\QualIT-AKL\\Desktop\\111\\yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
(node:11268) UnhandledPromiseRejectionWarning: Error: null
at _inquirer.default.prompt.then.answers (C:\Users\QualIT-AKL\Desktop\111\node_modules\#wdio\cli\build\setup.js:57:15)
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:11268) 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:11268) [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 have tried close all windows and disable firewall and antivirus but still no working, I might need a little help here and thanks in advance.

I guess I ran 'wbio config' under '.bin' folder causes EBUSY.
Use node_modules\.bin\wdio config under '111' folder resolved the issue.

Related

Error when I want to create react app: error Couldn't find package "jest-watch-typeahead#^1.0.0" required by "react-scripts" on the "npm" registry

I get this error when I use CRA and I start it with yarn. Although I searched for that on the stack I can't find a solution for that:
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
error Couldn't find package "jest-watch-typeahead#^1.0.0" required by "react-scripts" on the "npm" registry.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
Aborting installation.
yarnpkg add --exact react react-dom react-scripts cra-template --cwd F:\projects\notes has failed.
Deleting generated file... package.json
Deleting notes/ from F:\projects
Done.
error Command failed.
Exit code: 1
Command: C:\Users\arman\AppData\Local\Yarn\bin\create-react-app
Arguments: notes
Directory: F:\projects
Output:
info Visit https://yarnpkg.com/en/docs/cli/create for documentation about this command.
It says about network connections, but my connection doesn't have any problem and I ran it several times. Is it possible that my problem is sanctions against Iran?
What's the problem and what do I have to do for fixing it?

Gatsby website built but 'UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'split' of undefined at parseError' when opening localhost

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

How to solve make × ERR not found: make-$(SOURCE_FILES) while running npm run build command

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?

Error: ": Unexpected token \u0000 in JSON at position 0" when using yarn to add a react package

I am trying to install the following package through yarn yarn add react-native-gesture-handler#1.10.2. I read multiple answers to this question yet none was of use. I think the problem might come from the fact I am on a windows computer yet don't know how to solve it.
Whenenever y try to do a yarn add ..#version I get the following error:
yarn add v1.22.11
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is
advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "C:\\Users\\...\\AppData\\Local\\Yarn\\Cache\\v6\\npm-unbox-primitive-1.0.1-085e215625ec3162574dc8859abee78a59b14471-integrity\\node_modules\\unbox-primitive\\.yarn-metadata.json:
Unexpected token \u0000 in JSON at position 0".
info If you think this is a bug, please open a bug report with the information provided in "C:\\Users\\...\\OneDrive\\Documents\\GitHub\\wc_app\\yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
I have same problem with installing next.js app many times
now its fixed
with clear cache of yarn
yarn cache clean
I have faced a similar problem while creating a latest react native project(0.65) in my Windows machine:
error An unexpected error occurred: "C:\Users\arefin\AppData\Local\Yarn\Cache\v6\npm-is-ci-3.0.0-c7e7be3c9d8eef7d0fa144390bd1e4b88dc4c994-integrity\node_modules\is-ci\.yarn-metadata.json: Unexpected token \u0000 in JSON at position 0".
My system configuration for react native development is as follows:
node --version: v15.7.0
yarn --version: 1.22.5
npm --version: 7.12.1
java --version: java 15.0.2 2021-01-19
I used these commands below, which finally solved the problem in my case:
yarn init && yarn add react-native && yarn react-native init
SpendnGain
which I found at here

error: bundling failed: ReferenceError: Module not registered in graph

i am a newbe in react native
i don't know what is going on with my apps
the node said "error: bundling failed: ReferenceError: Module not registered in graph"
please helpenter image description here
This error usually occurs when you install a new module (while packager is open).
Firstly you can try close your packager and run react-native run-ios. If this approach does not help, you can try delete node modules directory and npm install again. But i believe first approach will work.