einarq
@einarq.bsky.social
Long time frontend developer (20+ years), enthusiastic climber, father of two, husband of one. Enjoying React, Node, and Module Federation to create ambitious UX.
Principal frontend engineer at Forsta.
Principal frontend engineer at Forsta.
@en-js.bsky.social
I guess this is the relevant bug for the thing I was asking about earlier:
github.com/facebook/rea...
I guess this is the relevant bug for the thing I was asking about earlier:
github.com/facebook/rea...
[Compiler Bug]: `react-hooks/preserve-manual-memoization` is triggered for state setter depending on position of `useState` · Issue #34957 · facebook/react
What kind of issue is this? React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization) babel-plugin-react-compiler (build issue installing or using the Babel...
github.com
November 26, 2025 at 10:40 AM
@en-js.bsky.social
I guess this is the relevant bug for the thing I was asking about earlier:
github.com/facebook/rea...
I guess this is the relevant bug for the thing I was asking about earlier:
github.com/facebook/rea...
Maybe pull connect out in a separate “compat” package in a major?
November 23, 2025 at 7:44 PM
Maybe pull connect out in a separate “compat” package in a major?
Oops! 😅
It’s the right thing to do, it’s time 🙂
It’s the right thing to do, it’s time 🙂
November 23, 2025 at 12:48 AM
Oops! 😅
It’s the right thing to do, it’s time 🙂
It’s the right thing to do, it’s time 🙂
Yes. Still like it. Especially for code navigation.
Tried switching to VS Code a few times but just doesn’t feel as powerful, even with all the recommended plugins.
But you need a powerful machine to run it smoothly.
Tried switching to VS Code a few times but just doesn’t feel as powerful, even with all the recommended plugins.
But you need a powerful machine to run it smoothly.
November 21, 2025 at 11:46 PM
Yes. Still like it. Especially for code navigation.
Tried switching to VS Code a few times but just doesn’t feel as powerful, even with all the recommended plugins.
But you need a powerful machine to run it smoothly.
Tried switching to VS Code a few times but just doesn’t feel as powerful, even with all the recommended plugins.
But you need a powerful machine to run it smoothly.
Also hoping that Concurrent Stores will eventually make the Redux + Transitions story more viable. So far it’s seemed to me that transitions can only work if React controls the state, which of course is not the case for us.
November 21, 2025 at 11:42 PM
Also hoping that Concurrent Stores will eventually make the Redux + Transitions story more viable. So far it’s seemed to me that transitions can only work if React controls the state, which of course is not the case for us.
Very cool. Although gotta say, gonna have to read it a few more times to groc it 🤷🏼♂️😅
Our apps tend to use Redux and RTKQ, which uses uSES under the hood I think. Will that mean it cannot be enabled? Or does it depend on how and where we use Redux? Needs to be tested I guess.
Our apps tend to use Redux and RTKQ, which uses uSES under the hood I think. Will that mean it cannot be enabled? Or does it depend on how and where we use Redux? Needs to be tested I guess.
November 21, 2025 at 11:40 PM
Very cool. Although gotta say, gonna have to read it a few more times to groc it 🤷🏼♂️😅
Our apps tend to use Redux and RTKQ, which uses uSES under the hood I think. Will that mean it cannot be enabled? Or does it depend on how and where we use Redux? Needs to be tested I guess.
Our apps tend to use Redux and RTKQ, which uses uSES under the hood I think. Will that mean it cannot be enabled? Or does it depend on how and where we use Redux? Needs to be tested I guess.
I ended up removing the useCallback and switching to the "set state in render" recommendation anyway, so just curios.
react.dev/learn/you-mi...
react.dev/learn/you-mi...
You Might Not Need an Effect – React
The library for web and native user interfaces
react.dev
October 7, 2025 at 8:03 AM
I ended up removing the useCallback and switching to the "set state in render" recommendation anyway, so just curios.
react.dev/learn/you-mi...
react.dev/learn/you-mi...
Why does the "preserve-manual-memoization" rule require that we add state setters to the useCallback deps?
October 7, 2025 at 8:01 AM
Why does the "preserve-manual-memoization" rule require that we add state setters to the useCallback deps?
I guess the 'react-hooks/react-compiler' rule is completely gone now?
October 4, 2025 at 11:39 AM
I guess the 'react-hooks/react-compiler' rule is completely gone now?
We were on React 18, eslint-plugin-react-hooks ^6.0.0-rc.1, and react-compiler-runtime 19.1.0-rc.3.
Suddenly our linter is failing all over the place with "Definition for rule 'react-hooks/react-compiler' was not found.
Suddenly our linter is failing all over the place with "Definition for rule 'react-hooks/react-compiler' was not found.
October 4, 2025 at 11:39 AM
We were on React 18, eslint-plugin-react-hooks ^6.0.0-rc.1, and react-compiler-runtime 19.1.0-rc.3.
Suddenly our linter is failing all over the place with "Definition for rule 'react-hooks/react-compiler' was not found.
Suddenly our linter is failing all over the place with "Definition for rule 'react-hooks/react-compiler' was not found.
Is it a drop-in replacement for the useNonReactiveCallback in the Bluesky codebase?
October 2, 2025 at 9:12 PM
Is it a drop-in replacement for the useNonReactiveCallback in the Bluesky codebase?
The “custom dataStrategy to do even more advanced stuff” sounds like an interesting blog post 🙂
July 13, 2025 at 7:44 AM
The “custom dataStrategy to do even more advanced stuff” sounds like an interesting blog post 🙂
So it’s using createBrowserRouter?
Or do you mean framework mode with loaders?
Or do you mean framework mode with loaders?
July 3, 2025 at 11:29 AM
So it’s using createBrowserRouter?
Or do you mean framework mode with loaders?
Or do you mean framework mode with loaders?
Could you share some examples of how to use it for non-forms stuff?
June 11, 2025 at 9:56 PM
Could you share some examples of how to use it for non-forms stuff?
What’s the module federation story with Parcel? Does it work with the new “core” package, probably with the runtime part I would guess in that case?
It’s great that there is a viable path now, but my point is more that there should have been one from the start if the team expected more adoption.
It’s great that there is a viable path now, but my point is more that there should have been one from the start if the team expected more adoption.
June 4, 2025 at 10:09 PM
What’s the module federation story with Parcel? Does it work with the new “core” package, probably with the runtime part I would guess in that case?
It’s great that there is a viable path now, but my point is more that there should have been one from the start if the team expected more adoption.
It’s great that there is a viable path now, but my point is more that there should have been one from the start if the team expected more adoption.
This is great, but migrating from Webpack or Vite is also not always feasible.
I think the React team have underestimated the size of the ecosystem, and how difficult it might be to completely migrated the stack of an existing app.
This is why RSC doesn’t have a lot of adoption yet imo.
I think the React team have underestimated the size of the ecosystem, and how difficult it might be to completely migrated the stack of an existing app.
This is why RSC doesn’t have a lot of adoption yet imo.
June 4, 2025 at 12:09 PM
This is great, but migrating from Webpack or Vite is also not always feasible.
I think the React team have underestimated the size of the ecosystem, and how difficult it might be to completely migrated the stack of an existing app.
This is why RSC doesn’t have a lot of adoption yet imo.
I think the React team have underestimated the size of the ecosystem, and how difficult it might be to completely migrated the stack of an existing app.
This is why RSC doesn’t have a lot of adoption yet imo.
If there was a Webpack plugin + Node adapter people could plug into their existing spas then that would facilitate it a lot more.
June 3, 2025 at 6:48 PM
If there was a Webpack plugin + Node adapter people could plug into their existing spas then that would facilitate it a lot more.
I’ve played with it Next for sure, but Next not an option for us.
Just don’t get this impression that devs “don’t get it” from the react team.
There aren’t a lot of ways to adopt it outside Next.
Support in Vite + React Router will help.
Just don’t get this impression that devs “don’t get it” from the react team.
There aren’t a lot of ways to adopt it outside Next.
Support in Vite + React Router will help.
June 3, 2025 at 6:47 PM
I’ve played with it Next for sure, but Next not an option for us.
Just don’t get this impression that devs “don’t get it” from the react team.
There aren’t a lot of ways to adopt it outside Next.
Support in Vite + React Router will help.
Just don’t get this impression that devs “don’t get it” from the react team.
There aren’t a lot of ways to adopt it outside Next.
Support in Vite + React Router will help.
The BFF? Node.
React + Webpack on the client.
React + Webpack on the client.
June 2, 2025 at 9:41 PM
The BFF? Node.
React + Webpack on the client.
React + Webpack on the client.
Had it for 10 years. Still waiting for a way to start using RSC.
June 2, 2025 at 5:44 PM
Had it for 10 years. Still waiting for a way to start using RSC.