Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
component blocking the website load
See original GitHub issueMy places api key is correct and has billing enabled. I am importing like this
import Autocomplete from 'react-google-autocomplete';
When I put this in my code:
<Autocomplete apiKey={API_KEY} onPlaceSelected={(place) => { console.log(place); }} />
the website freezes and gets stuck in a loop until the website crashes.
Issue Analytics
- State:
- Created a year ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
How to fix a website with blocked mixed content - Web security
The best strategy to avoid mixed content blocking is to serve all the content as HTTPS instead of HTTP. For your own domain,...
Read more >9 tricks to eliminate render blocking resources - LogRocket Blog
By reducing render blocking resources, you can shorten the critical rendering path and reduce page load times, thus improving UX and SEO.
Read more >Don't Load All Your Web Components at Once - codeburst
Mounting a large number of components on page load can therefore seriously degrade performance, especially if the user needs to wait 4+ seconds...
Read more >Allow or block access to websites - Google Support
As a Chrome Enterprise admin you can block and allow URLs so that users can only visit certain websites. Restricting users' internet access...
Read more >How To Fix Windows 10/11 Blocking Websites Issues
1. Make use of a VPN. 2. Switch to a public DNS. 3. Use IPs, not URLs.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@BrightonNgema @cheymonty @jmferreiratech Can you guys try out 2.7.0? I wrapped the problematic stuff into a condition to not work on react 18. It was a workaround right from the start, so no wonder it caused the issue. Meantime I’ll take a deeper look into the original issue and try to come up with a more robust fix.
Found out the issue. I will try to fix it asap and ship a new version.