I need help to fix the following issue . While practicing with react app I got this msg in console:
[Deprecation] SharedArrayBuffer will require cross-origin isolation as of M91, around May 2021. See https://developer.chrome.com/blog/enabling-shared-array-buffer/ for more details.
A
nyone experiencing this issue? And know how to implement it?
Unless you are using SharedArrayBuffer yourself, the message might be caused by React. See https://github.com/facebook/react/issues/20829 for more details. It's been fixed at React 17.0.2 but unfortunately it's not going to be backported to older versions.
The warning is to mitigate the trouble when SharedArrayBuffer is used after Chrome 92, but since the availability of window.SharedArrayBuffer is checked in older React versions, you will unlikely see the same issue.
The bottom line is, don't worry about the warning as far as you are confident that it is caused by React.
Related
I am using Angular 10 in my Electron app and after building a release version of my app I see the following errors below in the Chrome Inspector. Unfortunately I have no idea if it comes from Electron or Angular, or what it even tries to tell me. The non-production build just runs fine without the error.
Unfortunately I can't really see the stacktrace. Does anyone know what it is, or has a good approach how to pinpoint the cause of it? Thanks!
You can click on the arrow next to 'k'. It gives you a more detailed info about the error and what might have happened.
I am occasionally getting the above error logged in AWS lambda. Just curious about it and want to know how can I replicate it locally in nodejs12.
This means that one of your packages or yourself are using a deprecated feature as of that version of node.
You would need to figure out which module it is and see if there is a fix for the issue.
The packages themselves can fix the issue by changing anywhere they use ._headers to .getHeaders
That said, this is only a warning, this wont currently break anything but it's always better to upgrade.
So before the question I wanna point out that the only thing I could find on this issue was on this stackoverflow question. This issue suggest that this was an issue with wappalyzer, and it was fixed in version 4.0.1. however I am using wappalyzer version 5.1.4 and is up to date with this.
I am building a web-app based on the MEAN-stack, everything worked as intended for a long time, until this error kept poping up in my google-chrome console:
Everytime i would click in my app header, and use my front-end routing to load up different components / modules this error appears, however I dont see any issue with what the web-app presents to me (it's not like I am missing data)
More details on the error:
I have no idea whats going on, or where this issue comes from.
This was due to a failing plugin.
Disable all plugins, and enable them one at a time to find failing chrome extensions.
In this case it was the wappalyzer extension.
Our NoFlo graph components have suddenly compressed themselves all into one uneditable box that says "WaitForward". See attached image.
For a while, this was happening on every browser, except Opera, so I could go in there and update graphs. Then, a couple of weeks later, even Opera wouldn't render the components, so now I am unable to add anymore logic to existing NoFlo forms.
We barely touch code related to NoFlo, so I don't think anything changed in our environment. My theory is that browsers (such as Chrome, which used to be the one stable browser to use for editing) have been updated recently, and this tool needs some kind of an update in order to render properly. Yet I can find no reference to this issue on the NoFlo GitHub instructions, and it doesn't look like anyone is having that issue here on StackOverflow (until now, of course).
The error message in the console says::
"TypeError: this.node.getTransformToElement is not a function"
I plunked this error into Google and saw that others are experiencing this with something called clientIO, and that recent updates to Google Chrome are to blame, as Chrome has recently removed a core feature that allowed related js to function.
But ... how can I fix this? That is the question!
It looks like recent updates to Google Chrome are the culprit.
Taken straight from jointjs.com's website::
Link to announcement from jointjs.com
Announcement: getTransformToElement() polyfill Nov 12th, 2015
Unfortunately, a new version of Chrome (48) removes a feature that is core to JointJS/Rappid. This feature is the SVGGraphicsElement.getTransformToElement() function. The motivation behind removing the method is - according to the Chrome team - open issues about how this method is supposed to behave.
To overcome compatibility issues with future versions of Chrome, we prepared a polyfill that makes sure this method exists. Before a new version of JointJS/Rappid is released (or if you, for any reason, don't want to upgrade), include the following code before you load your application JavaScript:
SVGElement.prototype.getTransformToElement = SVGElement.prototype.getTransformToElement || function(toElement) {
return toElement.getScreenCTM().inverse().multiply(this.getScreenCTM());
};
I was unsure exactly where to put this code in my noflo directory. So I tried putting it at the tippy top of the "app/js/main.js" file. It seems to be working! (But advice for a better location is more than welcome.)
I hope this helps anyone else out there who is experiencing the same issue.
So, I keep getting this error on starting up Meteor.
connect.multipart() will be removed in connect 3.0
visit https://github.com/senchalabs/connect/wiki/Connect-3.0 for alternatives
connect.limit() will be removed in connect 3.0
It started happening after I added the moment package, I removed it but still got the error.
Thanks for the help.
What you are seeing is likely a warning & not an error. Its not likely from Meteor or Moment, but another package you might have.
It should not stop your app from starting up/working.
There are a lot of packages that use connect, such as iron-router. Its best to just wait for the package maintainer to update the code so the warning is removed.
Did you go the website that the warning told you to go to?
https://github.com/senchalabs/connect/wiki/Connect-3.0
It explains in detail what is going on, and how to fix it.
Note that if you're currently using connect.bodyParser(), you will still get the deprecation >warning for multipart. For now, you can ignore it since you should only see the warning message once at start up. If you want to avoid any warning messages, do this instead (which is what connect.bodyParser() will be in 3.0):
app.use(connect.urlencoded())
app.use(connect.json())
I was using express.bodyParser(), so in my solution I used
app.use(express.urlencoded())
app.use(express.json())
and it worked fine. No more warnings.