Fixed css/main.css route

[mikalai-s]

Motivation

When using docusaurus-start a server treats any request that ends with main.css as one to serve css/main.css. That could break some custom assets in static dir that also have main.css name.

Have you read the Contributing Guidelines on pull requests?

Yes.

Test Plan

1. css/main.css is served:
   • run docusarus-start
   • ensured a home page loads css/main.css
2. css/main.css and custom main.css are served:
   • added api/main.css to static dir
   • updated siteConfig.js with separateCss: ["static/api"]
   • run docusarus-start
   • ensured both css/main.css and api/main.css are served

Related PRs

None.

[facebook-github-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[docusaurus-bot]

Deploy preview for docusaurus-preview ready!

Built with commit 63a4805

https://deploy-preview-904--docusaurus-preview.netlify.com

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

[endiliey]

Lgtm.