❌

Reading view

I built a free frontend interview trainer: 2,700+ questions with explanations

Hey everyone,

I've been preparing for frontend interviews and couldn't find a quiz tool I liked, so I built one: devsets.com

What's inside:

  • 2,700+ questions across 12 topics (JavaScript, TypeScript, React, Next.js, Angular, Vue, Svelte, HTML & CSS, state management, testing, patterns, system design)
  • Junior / Middle / Senior levels, and every answer comes with an explanation and links to the docs
  • Interview mode with a timer per question
  • Stack quizzes (e.g. "React Developer") that mix several topics like a real interview
  • Spaced repetition: questions you got wrong come back after 1, 3 and 7 days
  • 18 JavaScript coding tasks (debounce, deepClone, Promise.all...) with tests that run in the browser

It's free, ad-free and works without an account (sign in only if you want to sync progress). Available in English, Ukrainian and Polish.

I'd really appreciate feedback: wrong answers, confusing questions, missing topics, anything. Every question has a "report a problem" button too.

submitted by /u/Zealousideal-One-897 to r/reactjs
[link] [comments]
  •  

Did you remove your useMemo calls after turning on the React Compiler?

A few months ago I wrote about the React Compiler, and my advice for existing code was to leave useMemo and useCallback alone at first, then clean them up slowly, with tests, once the compiler has been running for a while.

I'm curious how that went for people who actually did it.

The public numbers I found are from InfoQ's write-up: Sanity saw 20-30% less render time and latency on their Studio packages (1,231 of 1,411 components compiled on the first pass), and Wakelet's INP went from 275ms to 240ms.

If you're running it in production, did you rip out the manual memoization? Did anything break?

My article, if you want the details on the compiled output: https://neciudan.dev/react-compiler-explained

submitted by /u/creasta29 to r/reactjs
[link] [comments]
  •  

I built a client-side cache in Rust and compiled it to WebAssembly

I built a client-side cache in Rust and compiled it to WebAssembly

Hey everyone,

I built **Blaze Cache**, a client-side caching library written in Rust and compiled to WebAssembly.

The main idea was to get a fast, predictable cache in the browser with:

- Synchronous get/set after initialization (no Promises on the hot path)

- SIEVE eviction

- TTL + tag-based invalidation

- Optional IndexedDB persistence

- Adapters for Axios, fetch, TanStack Query, and SWR

I was mostly curious whether moving the cache core into Wasm would help with performance and structure compared to typical JS cache implementations.

Would love feedback from people who’ve worked on caching, Wasm, or frontend performance.

GitHub: https://github.com/blaze-cache/blaze-cache

Docs: https://blaze-cache.github.io/docs/

submitted by /u/Brave_Magician2474 to r/reactjs
[link] [comments]
  •  
❌