Agree w @ben11kehoe {proxy+} is an anti pattern with one exception: doing ‘/‘ 404 catchall. (ht @ryan)
I think SSR JS is also an exception. Routing for us was too complex and difficult to duplicate in API Gateway.
-
-
Why give up a flexible fast enough router for a service that's hard to test?
-
Not sure tbh. We got it to work by packaging our front end as a node module that exports a single fn that returns a string for given route.
-
We then install that module in all the routes that render HTML. And then compile static assets to s3 for hydrate path. It works!
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.