preactjs / preactjs/preact-devtools
Log render reasons in browser console
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 345
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
I'm new to Preact.
Long time ago I was using React and it was almost necessary to use this tool to speed everything up: https://github.com/welldone-software/why-did-you-render.
Today I started working with Preact for the first time and I was wondering if today we still need a tool like that.
And if so, how can we make it work for Preact?
From here it seems to me that nobody knows how: https://github.com/welldone-software/why-did-you-render/issues/113.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by investigating how Preact render information could be exposed to the browser extension, then review the linked why-did-you-render discussion for compatibility constraints. Done means a defined approach exists and render reasons can be logged in the browser console.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100