[v2] re-rendering devours previous lines?
See original GitHub issueThis only seems to happen on Hyper for me, when using tmux with a log line and not all the time, but I managed to get a recording of it, and my npm pick-updates
npm branch seems to reproduce it for me fairly often.
Repro Steps
- Get Hyper and tmux
git clone https://github.com/npm/cli && cd cli
make link
npm pick-updates
- Move your cursor around.
Results
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
How to prevent re-rendering of components that have not ...
Personally I would avoid React.memo / React.useRef / React.useCallback . The simplest solution to your example is just create another ...
Read more >How to check if your component rerendered - and why!
Using React DevTools to highlight what components rerendered. There's a checkbox well hidden in the React DevTools settings that allows you to ...
Read more >React re-renders guide: everything, all at once
Comprehensive guide on React re-renders. The guide explains what are re-renders, what is necessary and unnecessary re-render, ...
Read more >Re-rendering Components in ReactJS
React components automatically re-render whenever there is a change in their state or props. A simple update of the state, from anywhere in...
Read more >How to debug unnecessary rerenders in React | Bryce's Blog
After you end the Profiler session, you'll be able to drill down into individual components to see their render metrics. Under the “Why...
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
After implementing 3 different functions for wrapping terminal output, I decided to try to patch
wrap-ansi
itself: https://github.com/chalk/wrap-ansi/pull/29. It still has one issue left to fix, but I thought it would be useful to give you an update and a way to track progress of this issue.Fixed in 2.0.0-17!