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

[ramazansancar]

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. 😊

You’re absolutely right to notice the differences between the JavaScript (JS) and TypeScript (TS) code examples in the providers documentation. The distinction you pointed out—specifically the use of baseUrl and rootPath in the JS example—reflects different ways of configuring provider options, and it can understandably be confusing.

What’s going on?

• In the JS example, the configuration for AWS S3 under /config/plugins.js uses:

  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'),
    },
  },

• In the TS example, the configuration under /config/plugins.ts is slightly different:

  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'),
  },

• This difference is present in the official documentation as well, in the Provider configuration for Email on Strapi Cloud.

Is this intentional or a mistake?

Based on the documentation, it appears that the examples are meant to illustrate different possible configurations, but the inconsistency between JS and TS could be confusing and may not be intentional. The documentation does not explicitly explain why these differences exist, nor does it clarify which structure is preferred or required for each language. Therefore, it’s possible this is an oversight or a documentation bug rather than a deliberate choice.

What should you do?

• Both configuration styles are valid as long as they match the requirements of the provider you are using. However, for consistency and clarity, it would be best if the documentation examples matched unless there is a technical reason for the difference.
• If you’re unsure which structure to use, refer to the provider’s npm package documentation or the Strapi Upload provider docs for the most up-to-date configuration options.

Next steps:

• I’ll flag this for the documentation team to review and clarify the examples. If you’d like to suggest a specific improvement, you’re welcome to open a pull request or share your suggestion on Strapi’s feedback portal.
• If you run into any issues with the configuration itself, feel free to ask for help on the Strapi Forum or Discord—the community and core team are always happy to help!

Thank you again for your keen eye and for helping improve Strapi’s documentation. If you have any more questions or suggestions, please let us know! 🚀

If this turns out to be a product bug or core functionality issue rather than just documentation, please let us know so we can transfer it to the appropriate repository and tag @pwizla for further review.

📚 Relevant documentation:

• Adding TypeScript support to existing Strapi projects
• Community & Support
• Email Providers - Configuration per environment
• Email Providers - Configuring providers
• Environment configuration and variables - Environment configurations
• Frequently Asked Questions - Can I use TypeScript in a Strapi project?
• How to access to configuration values from the code
• Project structure
• Release notes - 5.2.0
• Release notes - 6.0.0-beta.2
• Server configuration - Configurations
• TypeScript
• TypeScript configuration
• Upload Provider - Configure the Provider

---

ℹ️ 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.

[ramazansancar]

The relevant page and code are not accessible. They have been deleted or moved to a different location. @pwizla

[pwizla]

Hi @ramazansancar, and thanks for pointing this out!
We indeed recently split the previous "providers" page into Media Library providers and Email providers, and I forgot to add redirections.

Here are the correct links:

• Providers configuration instructions for the Media Library:
  CMS → https://docs.strapi.io/cms/features/media-library#providers
  Cloud → https://docs.strapi.io/cloud/advanced/upload
• Providers configuration instructions for the Email feature
  CMS → https://docs.strapi.io/cms/features/email#providers
  Cloud → https://docs.strapi.io/cloud/advanced/email

I also updated the links in the AI-generated answer above.

Does that help?

[pwizla]

Also I catched the differences 👀
Based on the official AWS S3 provider readme, I'd say in our docs at docs.strapi.io we should have the config. example as such:

module.exports = ({ env }) => ({
  // ...
  upload: {
    config: {
      provider: 'aws-s3',
      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'),
          },
        },
      },
      actionOptions: {
        upload: {},
        uploadStream: {},
        delete: {},
      },
    },
  },
  // ...
});

Do you confirm it works this way? I'll make JS and TS code examples consistent if it works.

[ramazansancar]

@pwizla Thanks for the support and information. I will check and provide information when I am available.

[ramazansancar]

@pwizla When I check it right now, it is configured as it works for us. The inconsistency between js and ts in the documentation seems to have been resolved. Thanks 🙌