Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2022-07-16

Channels

#reagent
<
2022-07-16
>
pinkfrog23:07:06

When using reagent/react, does it mean one is locked into SPA? I wonder how to achieve the result of having a website that routes on the backend (instead of using spa routing on the frontend js), and also enjoy some sort of js for each web page.

pinkfrog02:07:37

I am thinking about how to organize a website that: 1. Routing happens on the backend (so not spa) 2. Each different page , e.g., /page1, /about, /foobar shall have its own js, and also some global shared js 3. Further, these js are managed by shadow cljs if possible

p-himik02:07:58

You can use Reagent without making an SPA.

pinkfrog03:07:45

I am more interested in how to manage point 2.

pinkfrog04:07:29

If we ignore reagent/react, what is the proper management in the js tooling for that purpose? Something other than webpack

p-himik04:07:54

What do you mean by "management"?

p-himik05:07:56

If you're using shadow-cljs, you don't really have to use anything else, unless you have some special requirements like being able to use pure TypeScript packages.

pinkfrog09:07:10

Looking at it again, code splitting is really the key thing.

✅ 1
pinkfrog09:07:29

I can jack in with one alias (e.g.,), but working on multiple pages.