loco new for server rendered web application?

[mengelseatz]

Hi all
I played with loco a few months ago and when running loco new it gave me I think 3 options (similar to the loco cast on the homepage of loco.rs) but now there's several more options and none of them seem to generate a server rendered HTML web application? I think I tried all of them and the only option that was kind of close was the REST API but I'm trying to build a htmx based server rendered application. I would have thought Sass Server Rendered would be the one to do this but that still generates a frontend directory so I'm guessing that it's a server rendered react app?

Anyway - there's some gaps in the documentation and the loco casts because these options have changed. IMO they're also kind of unclear. Like I have no idea what lightweight-service or Advanced would possibly mean if I'm coming in as newbie.

Thanks for any pointers.

[kaplanelad]

Hey @mengelseatz,
I’m not sure I fully understand which template you're looking for.
If you need server-side rendering, you should select "SaaS App with Server-Side Rendering."
Let me know if you need any clarification!

[mengelseatz]

Thanks @kaplanelad ... Yes that kinda does what I'm looking for but it also includes an full ./frontend directory with react code which is what confused me - why is the server side rendered SaaS template including typescript code .. for example in ./frontend/src/index.tsx this is included which is a React SPA template:

import React from "react";
import ReactDOM from "react-dom/client";
import { LocoSplash } from "./LocoSplash";

import "./index.css";

const root = document.getElementById("root");

if (!root) {
  throw new Error("No root element found");
}

ReactDOM.createRoot(root).render(
  <React.StrictMode>
    <LocoSplash />
  </React.StrictMode>,
);

Maybe this is just a bug in the CLI tool?

[kaplanelad]

Got it.
We don't have a starter template for server-side rendering with React. The default server-side rendering setup is built with Tera and handles template rendering on the server.

If you'd like, it would be great to get from you an example project using React for server-side rendering. We could adding it to our documentation or, consider if it's easy to maintain, as part of the predefined templates.

[mengelseatz]

Sorry @kaplanelad I may have not said this clearly in my earlier posts. What I'm saying is that loco new when you select SaaS App with server side rendering creates that frontend directory which is not what I want. I don't want React anywhere near my server rendered code :)
Here's the command to create a new application

Here's the output of tree:

My expectation of running the above loco new is that there NOT be a frontend directory with react code created which isn't what is happening.

[kaplanelad]

This was fixed in PR #1224 and will be included in the next release.
The frontend folder will no longer be created when selecting Server-Side Rendering.

[mengelseatz]

Thanks!