How to get autoCodeSplitting lazy loading built into the generatedRouteTree file outside of dev mode or production build
#5789
jedwards1211
started this conversation in
General
Replies: 1 comment 1 reply
-
|
autoCodeSplitting only works with a supported bundler. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
It seems like
autoCodeSplitting: trueonly generates lazy loading for the in-memory files in dev mode or the production output.I want a
generatedRouteTreefile to have the lazy imports so that I can import my router directly in Node to usebuildLocation, without the overhead of loading virtually all of my React component modules, or having to use a transpiler or bundler to keep node from crashing on the.tsximports in the generated route tree file.Is there any way to do this?
There ought to be an easy, lightweight way to get a typesafe
buildLocationfunction in Node when doing file-based routing.If it were up to me I would use code-based routing since this would be easy to accomplish with code-based routing, but unfortunately some of my colleagues prefer the convenience of file-based routing despite its downsides.
Beta Was this translation helpful? Give feedback.
All reactions