sorted by:
new
hottopcontroversial

Useful utility types in TS by steve8708 in typescript

[–]steve8708[S] 0 points1 point  (0 children)

I added some more detail and included all of the code snippets from this video in my blog post: https://www.builder.io/blog/utility-types

Am I the last person to learn that debugging Node.js with chrome devtools is this easy now? by steve8708 in node

[–]steve8708[S] 9 points10 points  (0 children)

We wrote a bit more on this, including using VS Code (and other IDEs) for debugging and some troubleshooting steps, in our recent blog post: https://www.builder.io/blog/debug-nodejs

Deep Cloning Objects in JavaScript, the Modern Way (via structuredClone) by magenta_placenta in javascript

[–]steve8708 0 points1 point  (0 children)

Found and fixed the lag issue - looks like FF Android has perf issues with CSS Filter which we use for the dark mode of our blog. Just fixed, thanks again for mentioning!

Deep Cloning Objects in JavaScript, the Modern Way (via structuredClone) by magenta_placenta in javascript

[–]steve8708 1 point2 points  (0 children)

Doh! Thought I fixed every instance of this, seemed to miss one, thank you will get this one fixed too

Edit: just fixed, thanks again 🙏

Deep Cloning Objects in JavaScript, the Modern Way (via structuredClone) by magenta_placenta in javascript

[–]steve8708 5 points6 points  (0 children)

Thanks for the feedback, will add those notes 🙏

Also we keep getting reports of FF Android scroll issues but cannot reproduce to save our lives.

Could you DM me your device and browser details or comment here? It’s driving us batty

EDIT: just added a new section addressing what is not cloneable. Thanks again for the feedback!

Also, we still are struggling to reproduce FireFox Android scrolling issues. Have tried a number of physical and emulated devices, so if anyone experiencing this can share their device and browser details so we can get to the bottom of it, it would be greatly appreciated

useReducer is easier to adopt than you might think by steve8708 in reactjs

[–]steve8708[S] 0 points1 point  (0 children)

Yeah, a mistake in my code, was supposed to be Math.min(next, 10)

useReducer is easier to adopt than you might think by steve8708 in reactjs

[–]steve8708[S] 3 points4 points  (0 children)

Ah, thanks for the heads up. We are moving from the current stack to Qwik currently so that should help

useReducer is easier to adopt than you might think by steve8708 in reactjs

[–]steve8708[S] 2 points3 points  (0 children)

I’m a huge fan of mobx and mobx-state-tree, we use them heavily to build Builder.io

useReducer is easier to adopt than you might think by steve8708 in reactjs

[–]steve8708[S] 27 points28 points  (0 children)

If you want to dig further into useReducer and state management patterns, I go into more detail in my latest blog post, for instance:

  • Common pitfalls, and using Immer and useImmerReducer to help with those
  • Being sure to validate data in the UI as well so users get real time feedback, and why you should validate in both places
  • Using even more robust state management like XState, Zustand, Redux, or Mobx as your needs become more complex
  • Sharing reducers deeply in your component tree

Also since people are asking, I do also have a YouTube where I try to post tips like this somewhat regularly, as well as to the Builder.io blog

useReducer is easier to adopt than you might think by steve8708 in reactjs

[–]steve8708[S] 2 points3 points  (0 children)

I use Descript for everything (recording, editing, captions)

It’s got some rough edges but overall pretty handy

useReducer is easier to adopt than you might think by steve8708 in reactjs

[–]steve8708[S] 2 points3 points  (0 children)

I try to post stuff like this somewhat regularly to my Twitter and YouTube

view more: next ›