So I'm using `@payloadcms/plugin-cloud-storage` an...

Payload-Bot

last month

6

const storageAdapter = s3Adapter({
  config: {
    endpoint: process.env.NEXT_PUBLIC_S3_API_ENDPOINT,
    region: process.env.S3_REGION,
    forcePathStyle: true,
    credentials: {
      accessKeyId: process.env.S3_ACCESS_KEY_ID as string,
      secretAccessKey: process.env.S3_SECRET_ACCESS_KEY as string,
    },
  },
  bucket: process.env.NEXT_PUBLIC_S3_BUCKET as string,
  acl: "public-read",
});
console.log(storageAdapter);

• 

  denolfe

  Payload Team

  last month

  @livog Nothing should have changed. Let me. Look into this. What version of Payload are you running?

• 

  livog

  last month

  Running

  2.0.5
  

  
  

  Running with:

  
  

  admin: {
      user: Users.slug,
      bundler: viteBundler(),
    },
  editor: lexicalEditor({}),
    db: postgresAdapter({
      pool: {
        connectionString: process.env.DATABASE_URL,
      },
    }),

  
  

  if that makes any difference

• 

  _mm__

  last month

  @denolfe - experiencing a similar thing - the adapter is an empty object. I'm on

  
  
  payload@2.0.6

  and

  @payloadcms/plugin-cloud-storage@1.1.1

  and using the viteBundler

  
• 

  denolfe

  Payload Team

  last month

  If you swap to the webpack bundler, does it still occur?

• 

  _mm__

  last month

  @denolfe - yup, have switched and adapter error disappears. good enough to get up and running again thanks!

• 

  denolfe

  Payload Team

  last month

  Okay, tracking this issue here:

  https://github.com/payloadcms/plugin-cloud-storage/issues/80