Does anyone pay attention to this PR? This may be a very minor problem, please confirm whether it needs to be dealt with
@prakashsvmx

I made some attempts but didn't achieve any results. I also don't know how to test.
Or maybe we can think about it differently.
What does the .type directory in package.json represent? Can you explain that? Why would someone write a non-existent directory name?

But the directory ./dist/main/minio.d.ts exists relative to .type

I suspect this change led to a breaking type change from 8.0.5 where

export async function uploadFile({
  objectName,
  stream,
  contentType,
}: {
  objectName: string
  stream: Readable | Buffer | string
  contentType?: string
}) {
  return minioClient.putObject(BUCKET_NAME, objectName, stream, undefined, {
    'Content-Type': contentType,
    'Cache-Control': 'public, max-age=31536000', // 1 year
  })
}

now gives a type portability error in a ts project with composite: true.

And its not possible to annotate the return type explicitly, because UploadedObjectInfo is not exported as a type for usage.