I'm just trying to run a simple and empty react native project in android emulator but I'm getting this error anyone have any ideas?
error:
Error: C:\Users\Onur\Desktop\ReactNative\MemorizingApp\android\gradlew.bat exited with non-zero code: 1
Error: C:\Users\Onur\Desktop\ReactNative\MemorizingApp\android\gradlew.bat exited with non-zero code: 1
at ChildProcess.completionListener (C:\Users\Onur\Desktop\ReactNative\MemorizingApp\node_modules#expo\spawn-async\build\spawnAsync.js:52:23)
at Object.onceWrapper (node:events:628:26)
at ChildProcess.emit (node:events:513:28)
at ChildProcess.cp.emit (C:\Users\Onur\Desktop\ReactNative\MemorizingApp\node_modules\cross-spawn\lib\enoent.js:34:29)
at maybeClose (node:internal/child_process:1093:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
...
at Object.spawnAsync [as default] (C:\Users\Onur\Desktop\ReactNative\MemorizingApp\node_modules#expo\spawn-async\build\spawnAsync.js:17:21)
at spawnGradleAsync (C:\Users\Onur\Desktop\ReactNative\MemorizingApp\node_modules#expo\cli\build\src\start\platforms\android\gradle.js:72:46)
at Object.assembleAsync (C:\Users\Onur\Desktop\ReactNative\MemorizingApp\node_modules#expo\cli\build\src\start\platforms\android\gradle.js:52:18)
at runAndroidAsync (C:\Users\Onur\Desktop\ReactNative\MemorizingApp\node_modules#expo\cli\build\src\run\android\runAndroidAsync.js:31:24)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
Create an ANDROID_SDK_ROOT variable in your system variables.
Add a path to your android SDK.
Solved the issue for me
Related
I want to download some packages in atom ide, I am not able to do so.
I am getting following errors...
atom feature error image
Fetching featured packages failed.Hide output…
C:\Users\prits\AppData\Local\atom\app-1.63.1\resources\app\apm\lib\featured.js:60
packages = body.filter(function(pack) {
^
TypeError: body.filter is not a function
at C:\Users\prits\AppData\Local\atom\app-1.63.1\resources\app\apm\lib\featured.js:60:27
at Request._callback (C:\Users\prits\AppData\Local\atom\app-1.63.1\resources\app\apm\lib\request.js:57:22)
at Request.self.callback (C:\Users\prits\AppData\Local\atom\app-1.63.1\resources\app\apm\node_modules\request\request.js:185:22)
at Request.emit (events.js:223:5)
at Request.<anonymous> (C:\Users\prits\AppData\Local\atom\app-1.63.1\resources\app\apm\node_modules\request\request.js:1154:10)
at Request.emit (events.js:223:5)
at IncomingMessage.<anonymous> (C:\Users\prits\AppData\Local\atom\app-1.63.1\resources\app\apm\node_modules\request\request.js:1076:12)
at Object.onceWrapper (events.js:312:28)
at IncomingMessage.emit (events.js:228:7)
at endReadableNT (_stream_readable.js:1185:12)
I was trying to download so packages in atom ide
I'm following the instructions on the official polymer page:
https://www.polymer-project.org/1.0/start/toolbox/set-up
but when I execute this command:
polymer init starter-kit
I receive this error:
error: [init] Template polymer-init-starter-kit:app not found
error: [cli.main] cli runtime exception: Error: Template polymer-init-starter-kit:app not found
error: [cli.main] Error: Template polymer-init-starter-kit:app not found
at Object. (C:\Users\ruben\AppData\Roaming\npm\node_modules\polymer-cli\lib\init\init.js:223:19)
at Generator.next ()
at fulfilled (C:\Users\ruben\AppData\Roaming\npm\node_modules\polymer-cli\lib\init\init.js:17:58)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
at Function.Module.runMain (module.js:695:11)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3
my version polymer-cli: 1.7.2
my version node is: 8.11.2
my version npm is:5.6.0
my version bower is: 1.8.4
What am I doing wrong?
Thanks very much.
run this commands:
git clone https://github.com/Polymer/polymer-starter-kit.git
cd polymer-starter-kit
git checkout v2.2.0
bower install
regards
I get this error when trying to create a new react app.
Tried updating create-react-app using npm and reinstalling React.
C:\Users\Panduka\Documents\tests>create-react-app markdown
path.js:33
function normalizeStringWin32(path, allowAboveRoot) {
^
RangeError: Maximum call stack size exceeded
at normalizeStringWin32 (path.js:33:30)
at Object.resolve (path.js:338:20)
at getRootPath (C:\Users\Panduka\AppData\Roaming\npm\node_modules\create-react-app\node_modules\fs-extra\lib\mkdirs\win32.js:6:27)
at invalidWin32Path (C:\Users\Panduka\AppData\Roaming\npm\node_modules\create-react-app\node_modules\fs-extra\lib\mkdirs\win32.js:16:12)
at mkdirsSync (C:\Users\Panduka\AppData\Roaming\npm\node_modules\create-react-app\node_modules\fs-extra\lib\mkdirs\mkdirs-sync.js:15:39)
at mkdirsSync (C:\Users\Panduka\AppData\Roaming\npm\node_modules\create-react-app\node_modules\fs-extra\lib\mkdirs\mkdirs-sync.js:35:16)
at mkdirsSync (C:\Users\Panduka\AppData\Roaming\npm\node_modules\create-react-app\node_modules\fs-extra\lib\mkdirs\mkdirs-sync.js:36:9)
at mkdirsSync (C:\Users\Panduka\AppData\Roaming\npm\node_modules\create-react-app\node_modules\fs-extra\lib\mkdirs\mkdirs-sync.js:36:9)
at mkdirsSync (C:\Users\Panduka\AppData\Roaming\npm\node_modules\create-react-app\node_modules\fs-extra\lib\mkdirs\mkdirs-sync.js:36:9)
at mkdirsSync (C:\Users\Panduka\AppData\Roaming\npm\node_modules\create-react-app\node_modules\fs-extra\lib\mkdirs\mkdirs-sync.js:36:9)
Fixed this issue by disabling Windows Defender - Controlled Folder Access.
I faced a similar issue today and fixed with running: $ npm logout
Error Log:
4268 http fetch GET 404 https://registry.npmjs.org/#xtuc%2flong 549ms
4269 silly fetchPackageMetaData error for #xtuc/long#4.2.1 404 Not Found: #xtuc/long#4.2.1
4270 verbose stack RangeError: Maximum call stack size exceeded
4270 verbose stack at failedDependency (C:\Program Files\nodejs\node_modules\npm\lib\install\deps.js:378:27)
4270 verbose stack at failedDependency (C:\Program Files\nodejs\node_modules\npm\lib\install\deps.js:396:9)
4270 verbose stack at failedDependency (C:\Program Files\nodejs\node_modules\npm\lib\install\deps.js:396:9)
4270 verbose stack at failedDependency (C:\Program Files\nodejs\node_modules\npm\lib\install\deps.js:396:9)```
Disabling Controlled Folder access helped
Fixed this issue by using Windows Subsystem Linux.
BTW, my Windows Defender is controlled by my organization policies.
I am a beginner with Deployd (www.deployd.com). I am learning the book "Pro AngularJS" and I have followed at the beginning of chapter 6 all the instructions in order to open the Deployd dashboard in the browser but am getting errors at the command prompt and the dashboard's refuses to open in the browser.
The page keeps on loading till it stops and displays that the server is not found. I also followed the steps on Deployd's page and I still get the same errors.
The error I receive at the prompt is:
Unhandled rejection TypeError: Cannot read property 'insert' of undefined
at C:\Program Files\Deployd\node_modules\deployd\lib\db.js:262:8
at C:\Program Files\Deployd\node_modules\deployd\lib\db.js:155:12
at tryCatcher (C:\Program Files\Deployd\node_modules\deployd\node_modules\bl
uebird\js\main\util.js:24:31)
at Promise._settlePromiseFromHandler (C:\Program Files\Deployd\node_modules\
deployd\node_modules\bluebird\js\main\promise.js:454:31)
at Promise._settlePromiseAt (C:\Program Files\Deployd\node_modules\deployd\n
ode_modules\bluebird\js\main\promise.js:530:18)
at Promise._settlePromises (C:\Program Files\Deployd\node_modules\deployd\no
de_modules\bluebird\js\main\promise.js:646:14)
at Async._drainQueue (C:\Program Files\Deployd\node_modules\deployd\node_mod
ules\bluebird\js\main\async.js:79:16)
at Async._drainQueues (C:\Program Files\Deployd\node_modules\deployd\node_mo
dules\bluebird\js\main\async.js:89:10)
at Immediate.Async.drainQueues [as _onImmediate] (C:\Program Files\Deployd\n
ode_modules\deployd\node_modules\bluebird\js\main\async.js:14:14)
at processImmediate [as _immediateCallback] (timers.js:367:17)
Unhandled rejection TypeError: Cannot read property 'insert' of undefined
at C:\Program Files\Deployd\node_modules\deployd\lib\db.js:262:8
at C:\Program Files\Deployd\node_modules\deployd\lib\db.js:155:12
at tryCatcher (C:\Program Files\Deployd\node_modules\deployd\node_modules\bl
uebird\js\main\util.js:24:31)
at Promise._settlePromiseFromHandler (C:\Program Files\Deployd\node_modules\
deployd\node_modules\bluebird\js\main\promise.js:454:31)
at Promise._settlePromiseAt (C:\Program Files\Deployd\node_modules\deployd\n
ode_modules\bluebird\js\main\promise.js:530:18)
at Promise._settlePromises (C:\Program Files\Deployd\node_modules\deployd\no
de_modules\bluebird\js\main\promise.js:646:14)
at Async._drainQueue (C:\Program Files\Deployd\node_modules\deployd\node_mod
ules\bluebird\js\main\async.js:79:16)
at Async._drainQueues (C:\Program Files\Deployd\node_modules\deployd\node_mo
dules\bluebird\js\main\async.js:89:10)
at Immediate.Async.drainQueues [as _onImmediate] (C:\Program Files\Deployd\n
ode_modules\deployd\node_modules\bluebird\js\main\async.js:14:14)
at processImmediate [as _immediateCallback] (timers.js:367:17)
Note: any time I type a command at the Deployd console I get the following message at the prompt:
js-bson: Failed to load c++ bson extension, using pure JS version
before the results of the prompt appears. I don't know if it is also part of the problem. It is my first time trying to use Deployd so I have no clue what these errors mean.
Check your bson installation. If you have not noticed the bson errors in red letters in the console while installing
npm install deployd -g
try update with,
npm update
To get the bson package correctly installed in your system you need, python and c++ compilers in the right path in your system.
Here is the link that shows many options to get the bson package installed properly.
http://techtothepoint.blogspot.com/2015/03/npm-install-errors-buildreleasebson.html
I am having trouble running the unit tests. I simply trying to run unit test and it throws following error -
~\gulp\unit-tests.js:28
throw err;
^
Error in plugin '←[36mgulp-karma←[39m'
karma exited with code 1
at done (C:\WorProj\S1SurveyClient\S1SurveyClient\node_modules\gulp-karma\in
dex.js:56:30)
at ChildProcess.<anonymous> (C:\WorProj\S1SurveyClient\S1SurveyClient\node_m
odules\gulp-karma\index.js:82:7)
at ChildProcess.emit (events.js:98:17)
at Process.ChildProcess._handle.onexit (child_process.js:810:12)
I had a similar issue and the solution was to add the path to the tests to karma.conf.js. Something like this:
files: ['target/test/*.spec.js'],