Have ya'll consider ripping out some of the core m...
# general
s
Have ya'll consider ripping out some of the core modules to promote community managed SST constructs, or a separate "incubator" package.
f
Yeah for sure. We’ve not decided on the format, might even start with a page in the doc with a list of community constructs.
What do u have in mind just curious?
s
I was playing around with creating my own RemixSite construct, but I wanted to leverage a lot of the same concepts/utils/base constructs that are being utilised in the NextjsSite construct. Unfortunately I wasn't able to import some of these "internal" modules in a nice way. ESM imports blocked me stating that the files weren't a part of the exports declaration of your
@serverless-stack/resources
package. Generalising some of these utils and base constructs into a separate package might help with this.
It would be nice to prove concepts outside of your primary packages.
I started to copy and paste, but it was painful. Ended up doing my own checkout of
@serverless-stack/resources
and began to use
yalc
to help me test bed extensions of it against a local project.
Think there needs to be a wider consideration around contribution and community constructs etc.
I have managed to get my RemixSite up and running on CloudFront with Lambda@Edge at least...
But still integrating all the other loveliness that's been put into NextjsSite construct to make it much more seamless and support env variable substitution etc.
Also getting it so that you can just bootstrap a bare bones Remix Run App, without any Architect references, and have the Construct do the necessary wrapping with a Lambda@Edge package I created.
Think I've seen a few people in here talking about Remix. So hopefully it generates some interest.