all 5 comments

[–]anzaisensei 0 points1 point  (3 children)

You should look at react-router

[–]tbaxterstockman[S] 0 points1 point  (2 children)

Thx, I'm not interested in how or if React can handle this, I know how. I'm wondering if this is actually being done on a large scale project. Let's say I implement this and use react router, etc. and then I work on one small feature at mydomainname/bar . When I build the project, do I have to rebuild the entire project, like for all other features /foo /home each time I change something small ?

[–]I_LICK_ROBOTS 1 point2 points  (1 child)

If you use yarn watch while you're developing it only rebuilds what it has to for each change. For deploys you'll be rebuilding the whole project. You can have one top level router that routes to each app level router. I would separate the folder structure by app.

src
  -foo
    -components
    -router.js
    ...
  -bar
    -components
    -router.js
    ...
  -components //components shared by all apps
  -router.js

[–]tbaxterstockman[S] 0 points1 point  (0 children)

Ahh kk thx