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
Currently there is a template using SolidJS, however it's only CSR. Using jitar with SSR isn't very documented, so having an example for people to go off of would help.
The text was updated successfully, but these errors were encountered:
After some research and experimentation, it appears that it isn't currently possible to get SSR working with Jitar. However, we are actively working on a solution. Details are provided below.
The problem
All imports controlled by Jitar fail in SSR mode. This issue is caused by Jitar's current segmentation strategy, which requires remote module loading. This is prohibited by default in SolidJS, and for good reasons. I haven't found any configuration options to override this behavior (such as the --experimental-network-imports option for Node.js).
The solution
We are aware of the risks associated with remote module loading, and we're already working on a solution. In issue #296, we're developing a new caching strategy that relies exclusively on static imports. This approach will eliminate the need for remote module loading, making it easier to enable SSR.
Conclusion
We don't have a short-term solution at the moment, but we're actively working on a long-term fix.
Currently there is a template using SolidJS, however it's only CSR. Using jitar with SSR isn't very documented, so having an example for people to go off of would help.
The text was updated successfully, but these errors were encountered: