I've begun receiving a lot of errors in the console. This didnt impede development on a previous project for a while, but once it started causing premature exits I decided to see what a brand new project gave me. The same errors exist.
Errors:
- Websocket handshake failed: 'Connection' header is missing.
- Invalid host/origin header
- [WDS] Disconnected!
- Uncaught typeError: ___ is not a function
I'm completely at a loss on what to do for these errors, but it doesnt seem to be a code issue. maybe some libs or packages are not playing well?
any insight is helpful!
Related
I'm new to using cloudflare and wrangler. I've a project that I've been working on, and I'm now trying to deploy it using wrangler publish, but I keep running into issues. My product is coded in node.js, and I'm using version 2 of wrangler. When I execute wrangler publish I get:
Basic JavaScript project found. Skipping unnecessary build!
Error: Something went wrong with the request to Cloudflare...
Uncaught SyntaxError: Cannot use import statement outside a module
at worker.js:2Basic JavaScript project found. Skipping unnecessary build!
Error: Something went wrong with the request to Cloudflare...
Uncaught SyntaxError: Cannot use import statement outside a module
at worker.js:2
I've searched for a solution, and one of them that I found said to change module in wrangler.toml from type="javascript"to type="webpack" however that gives me a bunch of errors:
./node_modules/destroy/index.js
Module not found: Error: Can't resolve 'fs' ... Parsed request is a module...resolve as module
/Users/Desktop/APIs/cpiCalculator2/node_modules/destroy/node_modules doesn't exist or is not a directory
...
Error: webpack returned an error. You may be able to resolve this issue by running npm install.
I've tried reinstalling npm as it suggests and then wrangler publish again, but that just gives me the same error message.
I'm really not sure what the issue is, and I would really appreciate any help or advice on how to resolve this issue. Thank you!
Also, just a note, I'm not sure if this is affecting it, but I do have two other js documents in the main area of my project (where my index.js file is).
In relation to this post:
After upgrading from revit 21 to 22 in my company, we can no longer view anything else than the default 3D model in our forge viewer. Initially, i thought the issue arose due to this warning:
"Deprecated API usage: No "GlobalWorkerOptions.workerSrc" specified.".
However, i got that same message in the console of a working implementation i made today, leading me to believe that it has nothing to do with this warning at all.
However, i also see another warning:
"Warning: getOperatorList - ignoring errors during "GetOperatorList: page 0" task: "r: Cannot read properties of undefined (reading 'X')"."
I have tried creating a new nuxt app on Node version 14.9.0, implemented a forge viewer in accordance with the official v7 documentation, and the bug is no longer present.
I then tried to mimic that in my actual production app where the problem exists, by running it on Node version 14.9.0 instead of 10.0.0, getting rid of my entire forge implementation and implemented a simple viewer like above. That did not solve the problem, and i still see above warnings in the console.
The warning is thrown in pdf.worker.jss, which is loaded in via "webpack://adsk/node_modules/#adsk/pdfjs-dist/legacy/build/pdf.worker.jss".
I hope someone has a suggestion.
I randomly see expo start -ci --no-dev fail with Failed to load all assets.
I cleaned up my TS errors and its passing with no errors.
I have been debugging this for three days now and getting nowhere. The error gives no clue as to what is failing. "Extra Info" is blank. Device log shows nothing.
To make things worse, I gradually add packages and functions into my monorepo, and at some point the error appears. So I'm thinking - ok, so the error is with this file. Commenting it out, trying again to make sure - yes it now works. Uncommenting it to make sure it was the problem - No. It doesn't fail. It works.
Seems like I am not alone: Error on Expo - Failed to load all assets
I'm getting the following error after running stencil start and accessing the localhost url in my browser:
Uncaught Error: Module parse failed: Unexpected token (10:9)
You may need an appropriate loader to handle this file type.
|
| var getAccount = function getAccount() {
> return import('./theme/account');
| };
|
at Object../assets/js/app.js (bootstrap:83)
at __webpack_require__ (bootstrap:19)
at bootstrap:83
at bootstrap:83
(index):1064 Uncaught TypeError: window.stencilBootstrap is not a function
at (index):1064
This just started happening this morning, I was able to run stencil yesterday without any problems.
I've followed the steps here exactly:
https://developer.bigcommerce.com/stencil-docs/getting-started/installing-stencil
I've tried uninstalling stencil and reinstalling multiple times. I've also tried using a fresh clone of cornerstone multiple times in multiple different directories. I can't get rid of this error and have tried all of the troubleshooting suggestions from the docs. There are no errors in the terminal.
I'm on macOS High Sierra 10.13.6
Node Version: v.6.4.0
Any ideas on why I'm getting this error?
This is an issue on our end with the Cornerstone 3.1 release, which can be downloaded through GitHub but hasn't rolled out to production yet. We've got an engineering ticket in to address it, but in the meantime, you can roll back to the Cornerstone 3.0 release to bypass the error. Sorry for the trouble!
My web application started to error out yesterday when calling gapi.auth.authorize, and there is no code change. Below is the error stack:
Error: .Uu is not a function
mk#/scs/apps-static/_/js/k=oz.gapi.en.1gq98XyFUlU.O/m=client/rt=j/sv=1/d=1/ed=1/am=IQ/rs=AItRSTPj42_xcRHRghwn4h4H79TdCPg3pw/cb=gapi.loaded_0:234">https://apis.google.com//scs/apps-static//js/k=oz.gapi.en.1gq98XyFUlU.O/m=client/rt=j/sv=1/d=1/ed=1/am=IQ/rs=AItRSTPj42_xcRHRghwn4h4H79TdCPg3pw/cb=gapi.loaded_0:234
qA#/scs/apps-static//js/k=oz.gapi.en.1gq98XyFUlU.O/m=client/rt=j/sv=1/d=1/ed=1/am=IQ/rs=AItRSTPj42_xcRHRghwn4h4H79TdCPg3pw/cb=gapi.loaded_0:236">https://apis.google.com//scs/apps-static//js/k=oz.gapi.en.1gq98XyFUlU.O/m=client/rt=j/sv=1/d=1/ed=1/am=IQ/rs=AItRSTPj42_xcRHRghwn4h4H79TdCPg3pw/cb=gapi.loaded_0:236
.sk#/scs/apps-static/_/js/k=oz.gapi.en.1gq98XyFUlU.O/m=client/rt=j/sv=1/d=1/ed=1/am=IQ/rs=AItRSTPj42_xcRHRghwn4h4H79TdCPg3pw/cb=gapi.loaded_0:238">https://apis.google.com//scs/apps-static//js/k=oz.gapi.en.1gq98XyFUlU.O/m=client/rt=j/sv=1/d=1/ed=1/am=IQ/rs=AItRSTPj42_xcRHRghwn4h4H79TdCPg3pw/cb=gapi.loaded_0:238
Is anyone seeing the same problem? Not sure if Google is making any changes.
Google broke the JS client yesterday. It's being tracked here https://code.google.com/p/google-api-javascript-client/issues/detail?id=103