You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have created a Svelte project that uses markdown-based pages with KitDocs following the documentation here. The project works perfectly in the local environment. However, when deploying this project on AWS infrastructure using the SST(https://docs.sst.dev/what-is-sst) kit framework, I encounter 500 error pages.
It seems the meta and sidebar URLs aren't returning anything, leading to the errors.
Steps to Reproduce
Create a Svelte project with KitDocs as described in the documentation.
Deploy the project to AWS using the SST kit framework.
Visit the deployed site.
Expected Behavior
The site should display the markdown-based pages with the correct content, meta and sidebar information.
Actual Behavior
The site returns 500 error pages. The meta and sidebar URLs seem to be failing (returning empty response), causing the pages to break.
Description
I have created a Svelte project that uses markdown-based pages with KitDocs following the documentation here. The project works perfectly in the local environment. However, when deploying this project on AWS infrastructure using the SST(https://docs.sst.dev/what-is-sst) kit framework, I encounter 500 error pages.
It seems the meta and sidebar URLs aren't returning anything, leading to the errors.
Steps to Reproduce
Create a Svelte project with KitDocs as described in the documentation.
Deploy the project to AWS using the SST kit framework.
Visit the deployed site.
Expected Behavior
The site should display the markdown-based pages with the correct content, meta and sidebar information.
Actual Behavior
The site returns 500 error pages. The meta and sidebar URLs seem to be failing (returning empty response), causing the pages to break.
Additional Context
KitDocs version: 1.1.5
SST Kit version: 2.43.1
Appreciate your input on this.
The text was updated successfully, but these errors were encountered: