remix-ecommerce VS remix

Didn't get past Intro page in Remix docs. But you could probably stick your middle wares here: https://github.com/jacob-ebey/remix-ecommerce/blob/main/app/entry.server.tsx

Also, Remix sourcemaps didn't work with Cloudflare Workers, but it seems that it should be working already. I should double-check it!

Then in this Github issue, I found something new and flashy, Paraglide JS.

Relates to https://github.com/remix-run/remix/pull/3104

The main goal of this project was to learn something new in a fun way, so I've decided to use Remix for it, and oh my - it was perfect. I was amazed by how powerful it is by using just standard web features such as cookies, query parameters, and forms. Just remember to be cautious when picking a starter template for your project. I picked the default one, and later found out it wasn't supported by Netlify. As a result, I had to delete the entire repository and start the configuration process again. 🙈

Real time data update: Remix supports Server Sent Events e.g. https://github.com/remix-run/examples/tree/main/_official-realtime-app https://github.com/remix-run/remix/discussions/2622

Sometimes the best way to learn is by looking at examples, so we’re going to walk through this Remix issue from Nick Taylor.

You don't need NextJS for SSR. There are less opinionated alternatives like Remix that was built by the React Router team and is backed by Shopify now, you can use something like Razzle or one of its alternatives for semi-opinionated pure SSR or follow the Vite Docs and just do it yourself with express.

- I've found Remix's configurable routes helps to split very large Remix projects into independent features that scales well, when multiple server output bundles drops this will scale the deployments across serverless functions also. RFC. PR.