You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In every single one of my react-router project, I find myself wanting to use reveal for entry.server.tsx, but using handleRequest as-is (I just want to add more exports).
I would very much like my entry.server.tsx to be
import {handleRequest} from "@react-router/???";
export default handleRequest;
// My custom exports
Rather than the current abomination, which is essentially copy-pasting a good chunk of code in all my projects. I have actually resorted to :
import handleRequest from "../node_modules/@react-router/dev/dist/config/defaults/entry.server.node.tsx";
export default handleRequest;
and letting the bundler pull handleRequest itself. Which is not very clean either, but cleaner IMO.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In every single one of my react-router project, I find myself wanting to use reveal for entry.server.tsx, but using handleRequest as-is (I just want to add more exports).
I would very much like my
entry.server.tsx
to beRather than the current abomination, which is essentially copy-pasting a good chunk of code in all my projects. I have actually resorted to :
and letting the bundler pull handleRequest itself. Which is not very clean either, but cleaner IMO.
Could you consider exporting handleRequest ?
Beta Was this translation helpful? Give feedback.
All reactions