I have phantomjs installed from binaries and working, accessible through $PATH and MeteorJS latest version with Spiderable latest version.
I use package flow-router for routing and flow-layout for rendering.
I have all my publishers either returning cursors (through find method) or returning this.ready(), through I don't have any subscribe() on page which I test nether in page template code, routes code nor layout template code.
I have Meteor set up locally (with meteor command for run) and websockets working.
When I visit the page, I see phantomjs process running on background, with ps aux
After awhile I get this error in meteor server console:
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:
That's all; no stderr. It looks like there's non-ready subscriptions but I checked this thing thrice.
Any suggestions?
Related
When I try to run my localhost using yarn dev it shows this error:
yarn run v1.22.4 $ next -p 7777 ready - started server on
0.0.0.0:7777, url: http://localhost:7777 TypeError: _jestWorker.Worker is not a constructor
at Object.loadWebpackHook (D:\isc-web\isc-front\node_modules\next\dist\server\config-utils.js:67:20)
at Object.loadConfig [as default] (D:\isc-web\isc-front\node_modules\next\dist\server\config.js:332:29)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async NextServer.loadConfig (D:\isc-web\isc-front\node_modules\next\dist\server\next.js:112:22)
error Command failed with exit code 1. info Visit
https://yarnpkg.com/en/docs/cli/run for documentation about this
command.
It was all working fine before I did npm install --save-dev babel-plugin-styled-components even though I canceled the changes by using git checkout -- . but still got the same problem
If you cancelled dependency changes with git checkout your node_modules may still have the old dependencies installed. Try running npm i again to see if getting updated dependencies resolves the issue.
I can't tell much from this error message and I don't know how far along your project is... Have you seen the official Next.js + styled-components example? https://github.com/vercel/next.js/tree/canary/examples/with-styled-components
Perhaps if you try setting up the library this way instead?
I'm trying my hand at wordpress theme development with WPRig (on WAMP server).
After installing it as per the tutorials, I'm trying to run it with "npm run build". The gulp and composer tasks seem to complete without any issues and finally it says that the local server (and browser-sync) has started on my localhost, however when I hit the url on my browser(chrome/IE), it spins for a minute and times out.
I couldn't find any issue similar to this anywhere on google/stackoverflow or on the github issues page (https://github.com/wprig/wprig). I hate it when things fail silently !!
There is just one error message right at the start, however I assume the fallback mechanism takes over, hence there is no exit from the build process:
[00:15:00] Failed to load external module #babel/register
[00:15:00] Requiring external module babel-register
Finally I tried to investigate with gulp's verbose mode and got he below output.
C:\wamp64\www\wordpress\wp-content\themes\daddycool (wprig#1.0.4)
λ node --inspect-brk .\node_modules\.bin\gulp --verbose
Debugger listening on ws://127.0.0.1:9229/439d987c-37d1-46f2-81c3-1919a704d817
For help see https://nodejs.org/en/docs/inspector
Debugger attached.
C:\wamp64\www\wordpress\wp-content\themes\daddycool\node_modules\.bin\gulp:2
basedir=$(dirname "$(echo "$0" | sed -e 's,\\,/,g')")
^^^^^^^
SyntaxError: missing ) after argument list
at createScript (vm.js:80:10)
at Object.runInThisContext (vm.js:139:10)
at Module._compile (module.js:599:28)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
at Function.Module._load (module.js:489:3)
at Function.Module.runMain (module.js:676:10)
at startup (bootstrap_node.js:187:16)
at bootstrap_node.js:608:3
Waiting for the debugger to disconnect...
Other things tried - I have nuked my npm cache...
λ gulp -v
[00:31:53] Failed to load external module #babel/register
[00:31:53] Requiring external module babel-register
[00:31:54] CLI version 2.0.1
[00:31:54] Local version 4.0.0
This is the version of my gulpfile :https://github.com/wprig/wprig/blob/1c8966ec5727323e83e382588cf28aa7a958e51a/gulpfile.babel.js
OK, I went back and looked at Mr. Morten's videos again on the setup and realized that i was doing something wrong.
Essentially, I had no virtual domain for my homepage and my site was basically at http://localhost/wordpress
Whereas, I just only changed the name of proxyURL from wprig:8888 to wordpress:8888 which was obviously wrong. After changing that to 'localhost/wordpress', everything works.
Sorry, I am a beginner (when it comes to web development), so this wasn't obvious to me.
I am trying to deploy a Meteor project using Mup. Mup Setup worked fine, but when i used the command Mup Deploy i get the following error below:
(Note: I have tried multiple appPaths but i have found no solution)
Meteor Up: Production Quality Meteor Deployments
“ Checkout Kadira!
It's the best way to monitor performance of your app.
Visit: https://kadira.io/mup ”
Building Started: /srv/asm/
events.js:72
throw er; // Unhandled 'error' event
^
Error: spawn ENOENT
at errnoException (child_process.js:1011:11)
at Process.ChildProcess._handle.onexit (child_process.js:802:34)
Fixed. In order to correct this error i double checked app path:
// Location of app (local directory)
"app": "/srv/asm/",
and uninstalled Meteor, then reinstalled meteor, then ran mup deploy. All is now working correctly.
I'm trying to start a new mean stack application. However i only get this error when I'm running grunt to start the server:
[nodemon] v1.2.1
Running "watch" task
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: *.*
[nodemon] starting `node --debug server.js`
Waiting...
Debugger listening on port 5858
Mean app started on port 3000 (development) cluster.worker.id: 0
/Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/base.js:246
throw message;
^
TypeError: Cannot read property 'length' of undefined
at processResults (/Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/db.js:1581:31)
at /Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/db.js:1619:20
at /Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/db.js:1157:7
at /Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/db.js:1890:9
at Server.Base._callHandler (/Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/base.js:448:41)
at /Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/server.js:481:18
at MongoReply.parseBody (/Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5)
at null.<anonymous> (/Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/server.js:439:20)
at emit (events.js:107:17)
at null.<anonymous> (/Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:201:13)
[nodemon] app crashed - waiting for file changes before starting...
Have any one encountered this before? Can't find too many other people who have encountered this before.
I was also facing the same error and this info solves it.
"Upgrade to 3.8.23. 3.8.22 introduced better compatibility with mongodb server 3.0 by upgrading to latest version of the driver." credit to vkarpov15 from mongoose Github thread.
What I did was I edit my package.json to upgrade mongoose to "3.8.23". After I edited the package.json I ran npm install and bower install(just to make sure) again and that solved the problem.
I'm using meteor 0.6.4, node 0.10.12 and laika 0.2.8. I followed the instructions on the getting started page and I get this error:
injecting laika...
loading phantomjs...
cleaning up injected code
/Users/camilo/.nvm/v0.10.12/lib/node_modules/laika/lib/app.js:124
if(err) throw err;
^
Error: spawn ENOENT
at errnoException (child_process.js:980:11)
at Process.ChildProcess._handle.onexit (child_process.js:771:34)
I switched to laika 0.2.4 based on this question Fail to run laika framework for meteor and get the same error.
Edit
I'm using phantomjs 1.9.1 installed with homebrew
Edit 2
I updated laika to 0.2.13 and tried with mrt (I was using meteor) but now the problem is different. With laika -D I get this:
[laika log] accepting the following extensions: (js)
injecting laika...
loading phantomjs...
[app touch log]
[app touch log] Stand back while Meteorite does its thing
[app touch log]
[app touch log] Done installing smart packages
[app touch log] Ok, everything's ready. Here comes Meteor!
[app touch log] [[[[[ ~/Documents/Pruebas/Meteor/test ]]]]]
[app touch log] => Meteor server running on: http://localhost:25969/
After a while, this error appear:
phantom stderr:
phantom stderr: child_process.js:927
throw errnoException(process._errno, 'spawn');
^
Error: spawn EAGAIN
at errnoException (child_process.js:980:11)
at ChildProcess.spawn (child_process.js:927:11)
at exports.spawn (child_process.js:715:9)
at Object.<anonymous> (/Users/camilo/.nvm/v0.10.12/lib/node_modules/phantomjs/bin/phantomjs:12:10)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
phantom crash: code 8
I uninstalled phantomjs, put the phantomjs binary on the same project folder and tested again but get the same error.
After many attempts, apparently the problem was with phantomjs. Installing it with homebrew or putting the binary directly on the project doesn't work for me. After update laika to 0.2.14 and install phantomjs with sudo npm install -g phantomjs it worked.
This is not a phantomjs basic issue. But a issue with nodejs version used by laika.
Please update laika to 0.2.13 and run laika -D which gives some verbose logs. lets talk about after that.
Normally, if your project runs with meteor (not mrt), laika uses binary located at following location.
~/.meteor/tools/latest/bin/node