I want to use the experimental Insertable Stream for MediaStreamTrack API in my project, specifically, the MediaStreamTrackGenerator.
The compatibility chart says it's supported from Chrome 94, and I'm using Chrome 109 (on Windows) so I figured it would be okay.
However, when ran new MediaStreamTrackGenerator({kind: video}) in my local development version of my react app, I got the error:
'MediaStreamTrackGenerator' is not defined no-undef.
First thought this is a problem with my chrome version so I ran the same line in my devtools console, and it worked there.
Then I thought this is because my node, npm, or react version not supporting this feature, so I updated them all to the latest version and it didn't help.**
A weird detail is that this error only appears after I make changes in my code (and it hot-reloads) or that I open devtools for my react app.
Update: it seems like I just had to add windows. to it.
Related
I created the build of a MERN Stack application using the npm run build command, then I ran this built application on my default browser (Microsoft Edge) using the npm start command. I then installed the react devtools extension for Edge from Chrome. But when I enable react devtools on my react app, it does not activate and I get the message This page doesn’t appear to be using React.
If this seems wrong, follow the troubleshooting instructions. I don't understand why I get this error because my application is entirely designed in react on the frontend side. I don't know if it's because I got the wrong server start command .
You can try the following solution.
In Edge, right click on React devtools, go to Manage extensions, and select "Allow access to file URLs".
Also, it has been reported that a re-installation of react devtools and a restart of browser may help. By the way, react devtools is available in Microsoft Edge Add-ons, so you can just install it in Edge (since you said you installed it from Chrome).
Updating Chrome to last version worked for me.
Chrome version: 109.0.5414.119 (Official Build) (64-bit)
System version: Ubuntu 20.04.2 LTS
I'm trying to do a fresh install of nextjs on Windows (see command line screenshot) using gitbash and latest nodejs lts version (16.14.2). When running npm run dev everything seems to be in order.
However, after browsing to http://localhost:3000, I receive this:
I looked at Fresh NextJS App throwing errors before any changes but the version in that issue is next 11.1.1 whereas current is 12.1.4. At this point I'm pretty much stuck. =\
Turns out it was an issue with Chrome extensions. I disabled all of them and no longer received the error. One by one I re-enabled all of them but never found the source. =\
I am working with Speechly API in my react application. In that, I imported PushToTalkButton and PushToTalkButtonContainer from #speechly/react-ui and I have also configured from Speechly Playground it's working fine in Playground. Then I click on the button(PushToTalkButton) in react application it is not capturing my voice and not using the microphone. I tried to find out the problem with ErrorPanel but nothing is showing.
Could you try upgrading to version 1.2.4 by issuing npm install #speechly/react-ui#latest
Earlier versions were inadvertently coupled with a certain version of react-client package and might cause a problem you described.
I upgraded my Chrome to version 87. I no longer am seeing my React source code in DevTools. The React Chrome Extension is installed and permission to access local files is enabled. So what could be the problem?
I've installed PostgreSql, pgadmin4 came along with it first. It didn't work so I installed the latest version of pgadmin4 v4 again but still its the same. It was showing a fatal error message earlier which said "Failed to open the system default web browser. Is one installed?." After that, it somehow worked & it started in my IE when I set it as my default browser. I tried opening it in Firefox too setting it as default browser but the result was same.
It shows the following screen rather than the expected normal screen that should appear as soon as we start it.
To resolve the issue, use the Windows Registry Editor to reset the value of
HKEY_CLASSES_ROOT.css\Content Type
to
text/css
and then restart pgAdmin4.
Ref: https://www.pgadmin.org/faq/#6
Note: Use Chrome or Firefox latest version with pgAdmin4, IE11 does not support many latest HTML technologies, for example with IE11 you will not able to download the graphical explain plan.