SolidJS•2y ago

Any workarounds or guidance for circular dependency warnings?

I realize Vite issue, but I was able to resolve in SvelteKit and no such luck (yet) w/ SS. Specifically, inclusion if AWS S3 client module is resulting in a lot of circular dependency spew at build time. W/ Svelte using node adapter, just need to regular dep (instead of dev dependency) so module doesn't get rolled-up, resulting in clean build output. Everything seems to be working fine, but the number of warnings being generated is unsettling. Same problem w/ auth-core, but to much lesser extent. Somebody has to have run into this w/ SS given S3 client usage. Any workarounds for SS, or folks just ignoring? Related thread: https://github.com/aws/aws-sdk-js-v3/issues/4435

GitHub

Circular dependency in packages · Issue #4435 · aws/aws-sdk-js-v3

Checkboxes for prior research I've gone through Developer Guide and API reference I've checked AWS Forums and StackOverflow. I've searched for previous similar issues and di...

1 Reply

hotshoeOP•2y ago

I forgot to mention, I did try to externalize the modules in question like so (but has no effect):

export default defineConfig({
    build: {
        rollupOptions: {
            external: ["@prisma/client", "@aws-sdk/client-s3", "@aws-sdk/s3-request-presigner"]
        }
    },

export default defineConfig({
    build: {
        rollupOptions: {
            external: ["@prisma/client", "@aws-sdk/client-s3", "@aws-sdk/s3-request-presigner"]
        }
    },

Again, realize vite issue but I've had zero luck, but since was I was able to resolve issue for same modules in SvelteKit (as mentioned above), wondering if there's a clean SS workaround.

Gaming

Programming

Any workarounds or guidance for circular dependency warnings?