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.
v2.0.0 is extremely slow in comparaison of v1.1.1
See original GitHub issueHi 👋
First, thanks for this amazing project, we use it on all our codebases!
I noticed that since the latest update, the formatting (with prettier --write) is extremely slow to perform.
Before (1.1.1):
After (2.0.0):
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Dilated conv in v1.0.0 is too slow. · Issue #15054 - GitHub
Hi, i've ported my model to 1.0.0, then found out my model much slower then it on v0.4.1. So I did some tests...
Read more >HTTP/2 vs. HTTP/1.1: How do they affect web performance?
Learn how HTTP 1.1 slows web performance. Compare HTTP/2 vs. HTTP/1.1, learn why HTTP/2 is faster, and learn about the next HTTP version:...
Read more >How To Fix Google Chrome Slow Download Speed [Solved]
In this video, I will show you guys how to fix google chrome slow download speed. you can try this method on your...
Read more >Windows 10: How to Fix Slow Performance Issue After Update ...
So, how to fix this slow performance issue in Windows 10 to boost system ... For example: After clicking the Start Menu, it...
Read more >MQTTAgent Publish is slow as compare to FreeRTOS MQTT
0.0. But previous version I used to publish the same data using FreeRTOS MQTT V2.1.1 is much faster than the current coreMQTT Agent...
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
Hi, thanks for the info. Just so you know, as long as you’re only using TypeScript, there’s no harm staying on 1.1.1 for now. There’s only been two changes really, one was to add support for two more parsers (
babelandbabel-ts), the other was to change some methods used from the TypeScript API (9d88c9b4ed03e4e41dc13774d100a3584d75e3ec).I’ll investigate which change this came from asap!
2.2.0runs through the repo in 6 seconds, compared to 26 seconds in2.1.0. Thanks a lot for the quick fix!