I tried the steps for quick setup of firefox debugger at http://firefox-dev.tools/debugger/#quick-setup a few times but had the same problem.
I have pasted all my commands and warning (including error) messages in a gist at the bottom.
I suspect two things may cause the failure of the setting up.
when running curl -o- -L https://yarnpkg.com/install.sh | bash -s, I got warning message saying it is advised to not mix npm with yarn. However, I have not yet found out a way to separate them.
when running yarn, I got a lot of warning message saying the versions of packages are not matching, a lot of error messages for failing to run commands which I suspect to be the result of unmet packages but I can be wrong about it.
or what do you think the problem is?
could you give me some guidance on how to resolve this setting up problem? Thanks
please see the warning and error messages here in the gist.
https://gist.github.com/EmbraceLife/f84993112c5b4a894c30b0a4ba4bb4fc
it is advised to not mix npm with yarn
...in a single project. If you follow the instructions of cloning a clean repository and running yarn install inside, you should be fine.
I got a lot of warning message saying the versions of packages are not matching
I get these too, so I don't think anything is wrong on your end.
warning " > react-redux#5.0.7" has unmet peer dependency "redux#^2.0.0 || ^3.0.0 || ^4.0.0-0".
warning "devtools-launchpad > svg-inline-react#3.0.0" has incorrect peer dependency "react#^0.14.0 || ^15.0.0".
warning "devtools-launchpad > url-loader#0.5.9" has unmet peer dependency "file-loader#*".
warning " > eslint-plugin-mozilla#1.2.1" has unmet peer dependency "eslint-plugin-no-unsanitized#^3.0.0".
warning "devtools-reps > devtools-components > #storybook/react#3.4.8" has unmet peer dependency "babel-core#^6.26.0 || ^7.0.0-0".
warning "devtools-reps > devtools-components > #storybook/react#3.4.8" has unmet peer dependency "babel-runtime#>=6.0.0".
warning " > babel-jest#23.6.0" has unmet peer dependency "babel-core#^6.0.0 || ^7.0.0-0".
node-pre-gyp WARN Pre-built binaries not found for fsevents#1.2.4 and node#12.9.1 (node-v72 ABI, unknown) (falling back to source compile with node-gyp)
followed by a large number of build errors, ending with:
30 warnings and 14 errors generated.
make: *** [Release/obj.target/fse/fsevents.o] Error 1
gyp ERR! build error
...looks like a problem with your running node12 (the CI seems to be running with node10) but I'm not even sure lack of fsevents is fatal...
Listening for WS on localhost:8116, all traffic is proxied to localhost:6080
TCP connection failed: Error: connect ECONNREFUSED 127.0.0.1:6080
These messages in your output are expected - you're supposed to run a controlled instance of the browser that listens on port 6080, until you do the "launcher" page tries to connect and fails repeatedly.
Apart from the console messages, is there a problem or does the debugger work?
Related
Since I installed Ventura I've been having an impossible time with Yarn. This command works on a normal linux environment but will not work on either of my Ventura machines. I've tested this on all environments using the same version of yarn (i.e. 1.22.19) and of nodejs (i.e. 12.22.12).
% yarn add -D #quasar/quasar-app-extension-testing-unit-jest
yarn add v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
warning #quasar/quasar-app-extension-testing-unit-jest > babel-jest > #jest/transform > jest-haste-map > sane#4.1.0: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
warning #quasar/quasar-app-extension-testing-unit-jest > vue-jest > babel-plugin-transform-es2015-modules-commonjs > babel-runtime > core-js#2.6.12: core-js#<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
warning #quasar/quasar-app-extension-testing-unit-jest > jest > jest-cli > jest-config > jest-environment-jsdom > jsdom > w3c-hr-time#1.0.2: Use your platform's native performance.now() and performance.timeOrigin.
[3/5] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/typescript/-/typescript-4.2.2.tgz: incorrect data check".
info If you think this is a bug, please open a bug report with the information provided in "/Users/noeldacosta/repo/gitlab/netbuilder/cpd/cpd-portal/client/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
Context:
I am attempting to run the demo from Wundergraph on a work computer. When I get to installing Wundergraph with Yarn, it fails. The Wundergraph error is.
Internal Error: Error when performing the request
at ClientRequest.<Anonymous> (C:Users\{user name here}\AppData\Roaming\npm\node_modules\corepack\dist\corepack.js :3927:20)
at ClientRequest.emit (noe:events:390:28)
at TLSSocket.socketErrorListener (node:_http_client:447:9)
at TLSSocket.emit (node:events:390:20)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
With the socket issue, I am guessing there is a proxy or some other security issue on the client computer. I have successfully run the following on a separate, personal computer:
yarn global add #wundergraph/wunderctl#latest
No variation of yarn commands work on the work, computer (fails with any of the following):
yarn
yarn global add #wundergraph/wunderctl#latest
To eliminate possibilities:
On my local machine, yarn will not properly add path to wunderctl, which means searcing out the .exe to get the samples installed. This is a minor oversight in the demo, as the demo now works.
Does not matter if the command prompt is run as me or as administrator. It fails either way.
Fails on VPN and off, so VPN not the issue.
I can get things installed with NPM, but that appears to successfully install the .js files from Wundergraph and not the .exe. I am thinking this might be a clue.
I am going to work with others who say they have it installed and see how they did it, but that won't happen until next week. As I am contract and they are employees, it could end up being additional restrictions.
As this does it with yarn, as well as yarn {install command here}, I am guessing it is some check yarn does every time, or permissions on the yarn files themselves.
I know this is a long shot, but hoping someone encountered this and has found a way down the Rabbit Hole and then back out of wonderland. My fear is having to go full manual, edit the sample files heavily to eradicate yarn (for npm, most likely), have to wait until Wundergraph goes open source and grab the bits, work strictly from command line, or all of the above.
I have done a lot of searching for an answer before coming here.
I had the same problem with another package, with exactly the same error call stack.
First I updated NodeJS to the latest stable version 16.13.1 (I had 14.16.0). After that yarn showed signs of life:
yarn install v1.21.1
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
But then it failed with
RequestError: connect ETIMEDOUT {ip address}:443
at ClientRequest.<anonymous> (node_modules\got\source\request-as-event-emitter.js:178:14)
at Object.onceWrapper (node:events:510:26)
at ClientRequest.emit (node:events:402:35)
at ClientRequest.origin.emit (node_modules\got\node_modules\#szmarczak\http-timer\source\index.js:37:11)
at TLSSocket.socketErrorListener (node:_http_client:447:9)
at TLSSocket.emit (node:events:390:28)
That ip address was indeed unreachable due to a routing problem, after I fixed that all went well.
The first step in the TC build process is to run "yarn install" in the directory: D:\TeamCity\Agent\work\MyApp
this is successfull up until: [4/4] Rebuilding all packages...
at which point this error is thrown:
```[Step 1/5] error An unexpected error occurred: "D:\\TeamCity\\Agent\\work\\MyApp\\node_modules\\#babel\\runtime-corejs2\\node_modules\\core-js: UNKNOWN: unknown error, open 'D:\\TeamCity\\Agent\\temp\\buildTmp\\yarn--1592234614361-0.5350564069819825\\yarn'"```
From what I can tell here, its trying to open the temp folder, but cant? or cant find it?
This does not happen consistently. It seems to be random, or whenever there is an extended time between builds. We cannot determine a common pattern. To fix it, we just re-run the build.
We have tried 'yarn install --verbose' and 'yarn install --force' the former showed nothing usefull on output, and --force was a guess at best.
I'm hoping someone can give a bit more context as to exactly what that error might mean.
Screenshot of the error
I really need some help with what seems to be the most basic task (setting up the expo/react-native project). I've installed the expo-cli (v3.11.7), react-native (v2.0.1), watchman (v4.9.0) and node (v12.14.1). I've followed the tutorial up until the point where I need to run expo start and I get the following error:
Your project is in SDK version >= 33.0.0, but the expo package version seems to be older.
Error: node_modules directory is missing. Please run npm install in your project directory.
Couldn't start project. Please fix the errors and restart the project.
Set EXPO_DEBUG=true in your env to view the stack trace.
I've then run npm install and tried again but the same error pops up. I've removed the node_modules folder and that didn't work either.
Update:
When I npm install this is the error I'm seeing:
npm WARN deprecated core-js#1.2.7: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
npm ERR! code EPROTO
npm ERR! errno EPROTO
npm ERR! request to https://codeload.github.com/expo/react-native/tar.gz/sdk-36.0.0 failed, reason: write EPROTO 4521895360:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1544:SSL alert number 40
I've installed yarn (v1.21.1) and tried installing using this with the same error:
warning expo > fbemitter > fbjs > core-js#1.2.7: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
error An unexpected error occurred: "https://github.com/expo/react-native/archive/sdk-36.0.0.tar.gz: write EPROTO 4356277696:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1544:SSL alert number 40
Can anyone advise?
I've managed to solve the problem. I was trying to install over my home network, which apparently has some proxy restrictions! No idea why.
Someone advised me to try again but connected to another network or my mobile hotspot. I tried this and it worked! Problem solved. So I guess for any others that may be experiencing the same problem, try connecting to another network and see if that helps.
If this fails, then I suppose looking at the proxy configuration and making changes there may help. But I wouldn't advise doing this unless you know exactly what you're doing.
I get the following errors trying to install blueprintjs. What to do? I've installed react-addons-css-transition-group.
warning " > #blueprintjs/core#1.35.3" has unmet peer dependency "react-addons-css-transition-group#^15.0.1 || ^0.14".
warning "#blueprintjs/core > pure-render-decorator#1.2.1" has incorrect peer dependency "react#^15.0.0 || ^0.14.0".
If you're using yarn, it seems these warnings never go away, despite having correctly installed the dependencies. So if your app works then go ahead and ignore these warnings.