So after installing chrome 83 one of my pages in my app crashes. It says some of my props that's required is undefined. This only happens in chrome. I've tested in IE 11, Edge, Firefox and it works fine in those. It doesn't happen all the time either in chrome. Especially if i restart my localhost it might work a couple of times and then it starts breaking. I've also checked sha1d on master branch couple of weeks back and it also breaks there. This was never an issue before and started just recently. There has been no code changes for weeks related to that page. Any ideas what can cause this in chrome?
Based on what you are saying if problem only started happening recently in chrome, and this could be the failure of the prop-types library, its the library responsible for showing such a warning a required prop is undefined.
To make sure that it is indeed the problem of the prop-types library, you can switch environment to production, as this library should not work in prod. If indeed its the problem of this library you could try the following
Maybe try removing react dev tools and see if problem still happens
clean install of the library
update the library
Related
I'm running a node.js project on a localhost server, and I've been doing this for months without seeing this, but recently, I've been getting this warning when I open the inspector:
The deferred DOM Node could not be resolved to a valid node.
I usually go into the inspector on an element to check out some attribute, eventListener, or other info, but this warning is popping up and it doesn't take me to the element. It's been pretty annoying, and I don't really know why it started showing up or how to get rid of it. My only clue is that I was changing some initialization settings for my express sessions around the same time this appeared, but I'm not sure that this is related.
Has anyone else run into this before? How do you get rid of the warning?
Thanks!
In my case, closing and reopening the browser window fixed it
That might be due to a chrome extension interfering. Make sure you test in an environment with no extensions like incognito mode.
This can occur when debugging in Visual Studio. Usually, restarting the debugger solves the problem
Open it in a incognito mode in chrome works!
I'm seeing this in Microsoft Edge right now (chromium version).
Never been aware of seeing it before and I don't have any extensions installed in Edge.
It currently works in Chrome! It also works in Edge in the live website but not my local machine.
In other words 🤷.
I've been working on an Angular app for a couple months now, and recently I started seeing a condition where the app compiles without errors, but when it reloads in Chrome there's just a blank screen. Also, no errors in the console. When I look at the markup, I can see the tag for my root component, but nothing else renders. I'm fairly certain I should NOT see the tag for the root component, but rather the rendered HTML, right? So it loads index.html, then craps out without any indication of what the issue could be. I have been attempting to move my components out of app.module and into feature modules to clean things up, but when I reverse those changes I still can't get the app to load. I've tried stopping and restarting the live dev server, but still no joy.
I'd post code here, but there's a ton of code in this app, and I don't know where the problem is. Why would Angular refuse to render without any compile or console errors, or any indication of what I can do to fix this?? If anyone has any idea where I can start to look, I'll be happy to post code.
FYI, I'm using Angular CLI 7.2.3, Angular 7.2.2. I'm developing in Visual Studio Code with the latest updates on a Windows 10 machine. I should also say that this has happened a few times during development, but I was always able to figure out what was causing the problem.
As requested, here is my answer. It's a bit embarrassing, given that I've been doing web development for over 20 years, but I forgot that I had disabled some options in the Chrome debugger settings. So Angular WAS sending errors when I got the blank screens, I just couldn't see those errors because I had disabled them. Once I reset the options to the default for Chrome, I was able to see all of the errors causing the page not to render. I realized this when I loaded the app in IE Edge and was able to see the errors in the console. I figured if IE is showing me the errors, I must have disabled them in Chrome.
I've followed all steps here in order to debug RN app using WebStorm.
First time all worked: Chrome was opened and I was able to set breakpoints on WebStorm and to actual debug some code.
When I hit the debug button again on WebStorm, I got an error:
can't run debugger
I guess this is due to the fact that Chrome was not opened this time localhost:8081/debugger-ui
Since then tried much stuff (restarting Chrome, WebStorm, my Mac..). None helped.
I've downloaded Chrome again and now again WebStorm was able to open it. And again second time did not work.
I am able to debug manually using Chrome itself, but I'd really like to use WebStorm for debugging)
Any ideas how to tackle this?
Opening Chrome beforehand isn't working.
Looks similar to WEB-30438; the issue is fixed, fix will likely be available in the next 2017.3.3 EAP
I am attempting the Meteor/Angular2 tutorial here
If I make a change to a component the changes are not updated in the browser (Google Chrome); even if I do the following things...
Save changes and hard refresh browser.
Stop server and restart.
I have to clear the browser cache to get rid of the old data and load the new.
I'm pretty sure this should not be the case, as it creates a major problem for a developer.
This tutorial is using Angular2, Meteorjs, as well as a typescript compiler.
This is not an Angular issue.
My question is... Is the problem with meteorjs not triggering a hard refresh? Or could it perhaps be an issue with the typescript compiler?
Also, how could I fix this?
I'm running
Typescript Compiler: netanelgilad:angular2-typescript
Meteorjs: 1.2.2
Google Chrome: Version 47.0.2525.0 canary (64-bit)
UPDATE:
I tried a normal .js file and everything works as expected. This means its the Typescript Compiler: netanelgilad:angular2-typescript.
I'll check out the package and see what I can find.
If You are using
http-server
then this may be the issue of http-server as it always store the data in cache.
In my case i was using http-server and this problem occured.
You can fix it by selecting the disable cache option in developer tools(chrome).
Using the repo found here:
http://github.com/nkallen/screw-unit
and this commit:
cc41f3cf373d804b11519704faf1971370f43760
I get this screen when viewing the package's "EXAMPLE.html" file:
Basically all of the text showing how many tests were run and the describe/it clauses, and the test results are missing.
The same revision works fine on Safari and Firefox.
I found this report that seems related, but no follow-up:
http://groups.google.com/group/screw-unit/browse_thread/thread/f0e82f5d68acbf21
Any ideas?
Edit: I found that upgrading jquery from version 1.2.6 (included with package) to 1.4.2 results in a screen in which green/red tests show up. Unfortunately, the top header showing the number of total tests and failing tests does not show up.
For those who may be hitting the same problem, I've found that the Pivotal branch of Screw.Unit seems to give exactly the same output for EXAMPLE.html in both IE7 and FF. There are others to choose from as well.
Save yourself the trouble and use Jasmine. It runs on all browsers, offers custom matchers, works on all browsers, is offered by Pivotal Labs, and is wicked fast. Syntax is very close to Screw.Unit, so porting is not conceptually difficult.