Fix dependency conflicts for Vercel deployment and repair broken links

Author: MauritsBrinkman

.npmrc

@@ -0,0 +1,2 @@
+legacy-peer-deps=true
+auto-install-peers=true 

docs/integration/backend.md

@@ -172,4 +172,4 @@ app.post('/api/captide/generate', async (req, res) => {
 
 - Learn about [Frontend Integration](./frontend) to connect your backend with a frontend application
 - Check out the [API Reference](/docs/api) for detailed endpoint documentation
-- Explore advanced SDK features in the [SDK Reference](/docs/sdk) 
+- Explore advanced SDK features in the [SDK Reference](/docs/integration/backend) 

docs/quickstart.md

@@ -104,7 +104,7 @@ generateText();
 Now that you've seen how to make basic calls with both the API and SDK, you can:
 
 - Explore the [API Reference](/docs/api) for all available endpoints
-- Check out the [SDK Reference](/docs/sdk) for detailed documentation on all methods
+- Check out the [SDK Reference](/docs/integration/backend) for detailed documentation on all methods
 - Learn how to integrate Captide with [Backend Applications](./integration/backend)
 - Learn how to integrate Captide with [Frontend Applications](./integration/frontend)
 

package.json

@@ -25,8 +25,8 @@
     "docusaurus-theme-openapi-docs": "^4.3.7",
     "lucide-react": "^0.503.0",
     "prism-react-renderer": "^2.3.0",
-    "react": "^19.0.0",
-    "react-dom": "^19.0.0",
+    "react": "^18.2.0",
+    "react-dom": "^18.2.0",
     "react-redux": "^7.2.9",
     "redux": "^4.2.1",
     "redux-thunk": "^2.4.1",