[TEST] [Bug]: Difference between Js and TS codes in Providers document

[pwizla]

Link to the documentation page or resource

https://docs.strapi.io/cms/providers

Describe the bug

Hello, There are obvious differences between the JS code and the TS code here. Were they written this way on purpose? Or is there a mistake?

Code here: https://github.com/strapi/documentation/blob/main/docusaurus/docs/cms/providers.md#configuring-providers

baseUrl: env('CDN_URL'),
rootPath: env('CDN_ROOT_PATH'),

Additional context

No response

Suggested improvements or fixes

No response

Related issue(s)/PR(s)

No response

[github-actions]

🤖 I've analyzed your question and here's what I found:

Hi there! 👋

Thank you so much for taking the time to report this and for your attention to detail—it’s community members like you who help make Strapi better for everyone. We really appreciate you highlighting the differences between the JavaScript and TypeScript code examples in the Providers documentation.

About the Code Differences

You’re absolutely right: there are some differences between the JS and TS snippets in the Configuring Providers section. Specifically, the JavaScript example for AWS S3 includes baseUrl and rootPath inside providerOptions.s3Options, while the TypeScript example places accessKeyId, secretAccessKey, and region directly under providerOptions, omitting baseUrl and rootPath.

Here’s a quick comparison:

JavaScript Example:

providerOptions: {
  baseUrl: env('CDN_URL'),
  rootPath: env('CDN_ROOT_PATH'),
  s3Options: {
    credentials: {
      accessKeyId: env('AWS_ACCESS_KEY_ID'),
      secretAccessKey: env('AWS_ACCESS_SECRET'),
    },
    region: env('AWS_REGION'),
    params: {
      ACL: env('AWS_ACL', 'public-read'),
      signedUrlExpires: env('AWS_SIGNED_URL_EXPIRES', 15 * 60),
      Bucket: env('AWS_BUCKET'),
    },
  },
},

TypeScript Example:

providerOptions: {
  accessKeyId: env('AWS_ACCESS_KEY_ID'),
  secretAccessKey: env('AWS_ACCESS_SECRET'),
  region: env('AWS_REGION'),
  params: {
    ACL: env('AWS_ACL', 'public-read'),
    Bucket: env('AWS_BUCKET'),
  },
},

Is This Intentional?

Based on the official documentation, these differences are present as shown, but there’s no explicit note explaining why the structure varies between JS and TS. The documentation does mention that each provider may have different configuration requirements, and for community providers, you may need to pass the full package name and follow their specific options. However, the inconsistency between the two examples for the same provider (AWS S3) is not clarified, and this could indeed be confusing for users referencing these docs for implementation guidance. It’s possible this is an oversight or a documentation bug rather than intentional design Configuring providers.

What Should You Do?

• If you’re using the official AWS S3 provider, we recommend following the structure outlined in the provider’s npm page and the Strapi documentation.
• If you encounter issues with one structure, try the other—Strapi’s plugin system is flexible, but the provider’s documentation should be the source of truth.
• If you’re unsure, you can always ask for clarification in the Strapi Forum or on Discord.

Next Steps

• I’ll flag this for the documentation team to review and clarify the examples so they’re consistent and accurate.
• If you’d like to suggest a specific improvement or submit a pull request, that would be amazing! You can also submit feedback or feature requests at feedback.strapi.io.

Thank you again for your keen eye and for helping us improve Strapi’s documentation. If you have any more questions or need further assistance, please don’t hesitate to reach out. We’re here to help!

Warm regards,
The Strapi Team

---

If this turns out to be a product bug or core functionality issue rather than just documentation, I’ll tag @pwizla for a possible transfer to the strapi/strapi repository.

📚 Relevant documentation:

• Database migrations|Handling migrations with TypeScript code
• Release notes|6.0.0-beta.1
• Welcome to the Strapi CMS Documentation!|Welcome to the Strapi CMS Documentation!
• Release notes|Chore, fixes, typos, and other improvements
• Project structure|Project structure
• Release notes|6.0.0-beta.2
• Release notes|5.2.0
• TypeScript configuration|TypeScript configuration
• How to access to configuration values from the code|How to access to configuration values from the code
• Release notes|5.1.0
• Upload Provider|Configure the Provider
• Frequently Asked Questions|Can I use TypeScript in a Strapi project?
• TypeScript|TypeScript
• Email and Upload Providers|Configuring providers
• Community & Support|Community & Support

---

ℹ️ This response was generated automatically. If this doesn't fully answer your question or if you need further assistance, please mention @pwizla in a comment and a human maintainer will help you.

You can also try our interactive AI chat for more detailed assistance.

💡 For feature requests or product feedback, visit feedback.strapi.io.