I'm getting an intermittent error reported in the browser after upgrading to Meteor 1.2:
SyntaxError: expected expression, got '<'
The page then does not load.
No errors are reported in the logs, so I've no idea how to go about figuring out what could be wrong.
Could anyone suggest possible issues or ways to detect them?
I noticed that the ecmascript package hides the actual errors you can't really debug it, try to meteor remove ecmascript and you will see straightforward error. Fix and restore the package with meteor add ecmascript It worked for me.
Related
I am running Gatsby + WP and have not seen this error until updating my gatsby-source-wordpress plugin.
The error message does not give me any information about where this is occuring so I am compeltely stuck.
I tried simply clearing my cache but that didn't do anything.
I am not getting errors in my local environment, but I when I push this to Gatsby cloud the build fails and gives me the message.
I am not sure if my answer will be helpful to you. But I had the same error when I pushed my code which worked fine in my local environment.
After spending some time debugging, I realised that the problem that stopped building wasn't related to the error message at all.
After I fixed the bug I still got the same error but the build succeed. So I recommend you try to check another factor that might cause the build to fail.
I'm working in React on VSCode and installed Moment.js via npm. For reasons I'm sure are unrelated all of a sudden I started receiving console errors to the tune of this: console errors. After trying to solve the errors by working through some potentially troubling GSAP syntax, they all still remained. I used git reset --hard to get me back to a point at which I knew the app was fully functional but the errors have persisted. I don't know what could have happened! Here's the CodeSandbox, let me know if you spot anything funky!
Thanks,
Connor
I'm using a boilerplate next.js template provided by this commmand:
npx create-next-app .
The error I get when I try to type anything on the chrome devtools console:
Unhandled Runtime Error
EvalError: Possible side-effect in debug-evaluate
My question: Is there a way to ignore or completely fix this type of error?
First: The supposed "duplicate solution" is a closed question with no accepted answer. The only response doesn't really offer a solution.
What I have tried
Tested on both Microsoft Edge and Mozilla Firefox. They don't seem to have this problem. My chrome version is: Version 102.0.5005.63 (Official Build) (64-bit).
Tested create-react-app and a normal js/html app and both don't seem to trigger errors. I'm concluding that this error is unique to the nextjs/chrome combo.
Same problem happens on other windows computers. This means that this problem is possibly global
Disabling the "eager evaluation" option in the chrome devtools seems to have solved the problem. I'm still looking for a solution that doesn't involve the removal of this feature.
This error seems to have been fixed in the latest chrome version. If it happens again, you can disable the "eager evaluation" option in the chrome devtools to fix the issue.
I am using JxBrowser (6.23.1) on windows 10 and using the 64-bit library. however, when i startup the demo application I get the following Log message.
SEVERE: [0528/084716.632:ERROR:browser_process_stub.cpp(279)] NOT IMPLEMENTED
Can anyone shed light on this and whether this is an issue?
I have tried to find anything in relation to above error code, but did not find anything.
The browser_process_stub.cpp(279)] NOT IMPLEMENTED message means that Chromium engine tries to get access to the specific code of JxBrowser which is not implemented at the moment due to the fact that this functionality is not supported by JxBrowser at the moment. This method does not affect the existing JxBrowser functionality, so you can safely ignore this error message.
I have been trying to figure out an issue with spiderable for several hours now. I have it installed and running beautifully on my local machine, but once I deploy to production I get this error spiderable: phantomjs failed: null. As you can see, this is not very helpful in debugging the issue.
I have followed all the advice in this excellent post on Meteorpedia, but to no avail:
http://www.meteorpedia.com/read/spiderable/
To make it even more strange, when I run the phantomtest.js script found on the page linked above, everything runs without any issue.
What I would really like to do is to be able to log some debug output from PhantomJS as it's being called by spiderable, but I have no idea if that's even possible. I tried messing around with spiderable code to pass some additional debugging parameters to PhantomJS, but that didn't work for me.
Any input would be greatly appreciated.