Phew, an update on the

RemixSite

construct. I had to do some refactoring to it as Remix has a weird way of defining statics. I need to give them some feedback in regards to this. There is a distinction between a "public" folder and the browser build of the site. By default the browser build is nested within the public folder, but this path can be overridden by a config in the remix.config.js. The user can additionally override a few other items which may impact the synth. I've managed to account for these now. Deployments are working as expected, with all the statics are being resolved. You can see a distribution here: https://dn4cfz69lmu8q.cloudfront.net/

wow that's a lot of work

I've opened a draft PR in the interim. A more fully fledged PR with detailed description on the process and reasoning will come.

I’m v excited for this

wow that’s a lot of work

curious.. does Architect also had to all these cases?

i am also curious if you could use https://github.com/simonireilly/funk-stack/blob/main/lib/remix-stack.ts, because guy used CDK, so I would assume that only few things should be adjusted and it would be more than enough to just use

createRequestHandler from @remix-vendor/cdk

?

Solid questions, and I do have answers. I'll be providing a full PR description and breakdown of how Remix works and why I have gone with the proposed solution.

^^^^ this 👨‍👩‍👧‍👦