I am reading a ton of things on this issue but can't figure out the answer.
I am on hosting our app on Modulus. I am using ongoworks:spiderable and dfischer:phantomjs and getting the following error.
spiderable: phantomjs failed: Error: Command failed:
at ChildProcess.exithandler (child_process.js:658:15)
at ChildProcess.emit (events.js:98:17)
at maybeClose (child_process.js:766:16)
at Process.ChildProcess._handle.onexit (child_process.js:833:5)
stderr:
Since Google depreciated their AJAX crawling I really want to figure out how to fix this bug and move on.
Also, how do I test if my app is crawlable now since ?_escaped_fragment_= doesn't do anything anymore.
Thanks!
Related
I was trying to Integrate my Cypress scripts and execute in Browser Stack.
While executing the script from the Visual code terminal using browserstack-cypress run I am receiving the following error. Appreciate if someone can advise on how to resolve
Issue that shows is Erro: spwan npm ENOENT
Keeping "cache_dependencies": false in run_settings in browserstack.json may help. Reference: https://www.browserstack.com/docs/automate/cypress/npm-packages#npm-dependency-caching
I installed all the environment setups for nativescript angular but I can't create new project using tns create command when I tried it shows me a error like this can anyone pls help me to solve to error
While trying I got this below error
npm WARN deprecated request#2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated fsevents#1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm ERR! Unexpected end of JSON input while parsing near '...":"latest","#types/gu'
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 have been running on some problems since the last update (6.38.1). docpad seems to be broken on macosx the command "docpad run" or "docpad watch" returns the error (on the browser)
Error 15 (net::ERR_SOCKET_NOT_CONNECTED): Error unknown
when i try to access
http://localhost:9778
but "docpad server" works without problems, so maybe the error is the liverload module or other module for development... i'm not able to isolate this problem.
does anyone has the same problem and maybe a solution to share? i'm about to leave docpad because of this error :(
I want to start to work with foundation 4. So I installed Ruby and Sass.
After I installed Sass gem, I get the following error message on docpad generate:
error: An error occured:
Error: spawn ENOENT
at errnoException (child_process.js:948:11)
at Process.ChildProcess._handle.onexit (child_process.js:739:34)
→ [2013-05-31 13:23:20.812] [C:\Users\USERDIR\AppData\Roaming\npm\node_modules\docpad\out\lib\docpad.js] [DocPad.log]
error: An error occured:
Error: spawn ENOENT
at errnoException (child_process.js:948:11)
at Process.ChildProcess._handle.onexit (child_process.js:739:34)
→ [2013-05-31 13:23:20.820] [C:\Users\USERDIR\AppData\Roaming\npm\node_modules\docpad\out\lib\docpad.js] [DocPad.log]
I'd like to use sass for generating foundation inside docpad.
I've tried to use this foundation docpad skeleton: https://github.com/axyz/zurb-foundation.docpad
What can cause this and how could I solve it?
a bit old question, however I've just updated https://github.com/axyz/zurb-foundation.docpad in order to support foundation v4.3.2 right now it seems to work well.
however I had to switch from pure sass to the nodesass implementation (keeping updated manually the source of foundation, maybe it could be switched to a git submodule). I had to switch not only for performance reason, but also because i had problems with the sass plugin: it just get stuck during docpad run whenever there is some file to parse like example.css.scss
It's likely the same as this issue - https://github.com/docpad/docpad-plugin-sass/issues/6 - that being that DocPad was unable to automatically detect your sass installation path, so you'll have to specify it manually by adding the following to your docpad configuration file
plugins:
sass:
sassPath: 'theValue'
scssPath: 'theValue'
compass: 'theValue'