unionpdf
react-scan
| unionpdf | react-scan | |
|---|---|---|
| 3 | 22 | |
| 18 | 21,364 | |
| - | 1.0% | |
| 3.7 | 8.3 | |
| 3 months ago | 17 days ago | |
| TypeScript | TypeScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
unionpdf
-
Pdftool.org: modify pdfs offline in the browser
For anyone want to build a tool like this, you can try my WIP library here, it's based on Pdfium and Wasm, you can build a tool support editing and previewing with it.
https://github.com/jichang/unionpdf
- PDF Rendering Library for Web
-
UnionPDF: a WIP library for showing PDF with react
GitHub - jichang/unionpdf: A universal pdf render in React
react-scan
-
18 developer tools I use to improve my workflow
3. React Scan
-
I Don't Like Magic
Re: excessive useEffects, this article from React docs is great: https://react.dev/learn/you-might-not-need-an-effect
Re: unrefactorable, large components, you probably want to break these down into smaller pieces. This talk ("Composition is all you need") is an excellent guide on the topic: https://youtu.be/4KvbVq3Eg5w?si=1esmAtrJthois1uf
Re: performance, people overstate the performance overhead of VDOM. Badly performing React applications are virtually always due to bad implementations. React Scan is an excellent tool for tracking down components that need optimizing: https://react-scan.com/
Re: getting other people on the team to write good code, this is the biggest struggle IMO. Frontend is hard because there's a lot of bad ways to solve a problem, and co-workers will insist that their changes work so why invest more time into building things correctly. I've only found success here by first writing an entire feature with good patterns and pointing to it as reference for other teams. People are more willing to make changes if they find precedent in the codebase.
-
How I optimize my React Flow application
After the change, react-scan no longer complained about excessive component re-renders. But now, it complained about the Javascript/React hooks execution time took too long.
- Zustand x Context API: Quem Rerenderiza Menos?
-
React Performance Optimization
please look : React-Scan and Theo Browne's very useful video about this
-
Here's how the options are validated in react-scan source code.
In the example provided in react-scan repository, you will find this below code in aidenybai/react-scan/examples/sierpinski/src/index.jsx.
- React Scan v0.2.0: A new way to debug React performance problems
-
React Scan Notifications
- how long it took for the GPU to actually draw to the screen
This data is visualized in an easy to understand ranked bar chart.
We also tell you exactly what props, state, and context caused a component to render. And when a component could of been memoized to avoid all its renders.
You can start using React Scan in your React app in <1 min using our script tag- installation reference: https://react-scan.com
-
DOMParser() usage in react-scan source code.
iconSprite is assigned a value returned by DOMParser.documentElement. parseFromString accepts ICONS that is imported from packages/scan/src/web/assets/svgs/svgs.ts.
-
Bippy, a toolkit to hack into react internals.
react-scan helps you scan for React performance issues and eliminate slow renders in your app.
What are some alternatives?
react-time-based-rendering - Time-Based Rendering in React
bippy - ⚠️ hack into react internals
pdfjam - The pdfjam package for manipulating PDF files
reactive-calculator - A Reactive Calculator App developed with Reactjs & Mantine.
pdfmixtool
blog - Jeff Schnitzer's Blog