feat: major update - Markdown Editor, CodeMirror upgrades, SEO improvements, tool cleanup

- Added new Markdown Editor with live preview, GFM support, PDF/HTML/DOCX export
- Upgraded all paste fields to CodeMirror with syntax highlighting and expand/collapse
- Enhanced Object Editor with advanced URL fetching and preview mode
- Improved export views with syntax highlighting in Table/Object editors
- Implemented SEO improvements (FAQ schema, breadcrumbs, internal linking)
- Added Related Tools recommendations component
- Created custom 404 page with tool suggestions
- Consolidated tools: removed JSON, Serialize, CSV-JSON (merged into main editors)
- Updated documentation and cleaned up redundant files
- Updated release notes with user-centric improvements
This commit is contained in:
dwindown
2025-10-22 15:20:22 +07:00
parent 08d345eaeb
commit fb9c944366
40 changed files with 6927 additions and 1714 deletions

331
BACKEND_REQUIREMENTS.md Normal file
View File

@@ -0,0 +1,331 @@
# Backend Requirements for Production
## Question 2: Does Advanced URL Fetch Need Backend?
### Short Answer:
**YES, for production use with CORS-protected APIs, you need a backend proxy.**
### Long Answer:
## Current Situation (Frontend Only)
### ✅ What Works Without Backend:
1. **Public APIs with CORS enabled**
- JSONPlaceholder
- GitHub API (public endpoints)
- Any API with `Access-Control-Allow-Origin: *`
2. **Same-origin requests**
- Your own domain's API
- Example: `dewe.dev/api/*`
### ❌ What Doesn't Work Without Backend:
1. **CORS-protected APIs**
- Your `api.starsender.online`
- Most private/commercial APIs
- APIs without CORS headers
2. **Secure API keys**
- Exposing keys in frontend = security risk
- Anyone can see your API keys in browser
---
## Why You Need Backend
### 1. CORS Bypass
```
❌ Frontend → api.starsender.online
Browser blocks: CORS error
✅ Frontend → Your Backend → api.starsender.online
No CORS (server-to-server)
```
### 2. API Key Security
```
❌ Frontend stores API key
Visible in browser console
Anyone can steal it
✅ Backend stores API key
Hidden from users
Secure environment variables
```
### 3. Rate Limiting & Caching
```
✅ Backend can:
- Cache responses
- Implement rate limiting
- Log requests
- Add analytics
```
---
## Backend Architecture Options
### Option 1: Simple Proxy (Recommended)
**Tech Stack:** Node.js + Express
```javascript
// server.js
const express = require('express');
const axios = require('axios');
const cors = require('cors');
const app = express();
app.use(cors());
app.use(express.json());
// Proxy endpoint
app.post('/api/proxy', async (req, res) => {
try {
const { url, method, headers, body } = req.body;
// Make request to target API
const response = await axios({
method: method || 'GET',
url: url,
headers: headers || {},
data: body || undefined
});
res.json(response.data);
} catch (error) {
res.status(error.response?.status || 500).json({
error: error.message,
details: error.response?.data
});
}
});
app.listen(3000, () => {
console.log('Proxy server running on port 3000');
});
```
**Frontend Update:**
```javascript
// In handleFetchData function
const response = await fetch('https://your-backend.com/api/proxy', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({
url: url,
method: advancedOptions?.method || 'GET',
headers: advancedOptions?.headers || {},
body: advancedOptions?.body
})
});
```
---
### Option 2: Serverless Functions
**Platform:** Vercel, Netlify, AWS Lambda
```javascript
// api/proxy.js (Vercel/Netlify)
export default async function handler(req, res) {
if (req.method !== 'POST') {
return res.status(405).json({ error: 'Method not allowed' });
}
const { url, method, headers, body } = req.body;
try {
const response = await fetch(url, {
method: method || 'GET',
headers: headers || {},
body: body ? JSON.stringify(body) : undefined
});
const data = await response.json();
res.status(200).json(data);
} catch (error) {
res.status(500).json({ error: error.message });
}
}
```
---
### Option 3: Full Backend with Auth
**For PRO user management:**
```javascript
// server.js with authentication
const express = require('express');
const jwt = require('jsonwebtoken');
const axios = require('axios');
const app = express();
app.use(express.json());
// Middleware to check PRO status
const checkProUser = (req, res, next) => {
const token = req.headers.authorization?.split(' ')[1];
try {
const decoded = jwt.verify(token, process.env.JWT_SECRET);
req.user = decoded;
// Check if user is PRO
if (req.user.tier !== 'pro') {
return res.status(403).json({
error: 'PRO feature',
message: 'Upgrade to PRO to use advanced URL fetch'
});
}
next();
} catch (error) {
res.status(401).json({ error: 'Unauthorized' });
}
};
// Protected proxy endpoint
app.post('/api/proxy', checkProUser, async (req, res) => {
const { url, method, headers, body } = req.body;
// Only PRO users can use non-GET methods
if (method !== 'GET' && req.user.tier !== 'pro') {
return res.status(403).json({
error: 'PRO feature required for ' + method
});
}
try {
const response = await axios({
method: method || 'GET',
url: url,
headers: headers || {},
data: body || undefined
});
res.json(response.data);
} catch (error) {
res.status(error.response?.status || 500).json({
error: error.message
});
}
});
app.listen(3000);
```
---
## Implementation Roadmap
### Phase 1: Basic Proxy (Week 1)
- [ ] Set up Node.js/Express server
- [ ] Create `/api/proxy` endpoint
- [ ] Deploy to Vercel/Netlify
- [ ] Update frontend to use proxy
- [ ] Test with your API
### Phase 2: Security (Week 2)
- [ ] Add API key validation
- [ ] Implement rate limiting
- [ ] Add request logging
- [ ] Set up error handling
- [ ] Add CORS whitelist
### Phase 3: PRO Features (Week 3-4)
- [ ] Set up user authentication (JWT)
- [ ] Create user database (PostgreSQL/MongoDB)
- [ ] Implement tier checking (FREE/PRO)
- [ ] Add payment integration (Stripe)
- [ ] Update frontend to send auth tokens
### Phase 4: Advanced Features (Week 5+)
- [ ] Request caching (Redis)
- [ ] Analytics dashboard
- [ ] Usage limits per tier
- [ ] Webhook support
- [ ] API key management
---
## Cost Estimation
### Free Tier Options:
- **Vercel**: 100GB bandwidth/month
- **Netlify**: 100GB bandwidth/month
- **Railway**: $5/month credit
- **Render**: Free tier available
### Paid Options:
- **Vercel Pro**: $20/month
- **AWS Lambda**: Pay per request (~$0.20 per 1M requests)
- **DigitalOcean**: $5/month VPS
- **Heroku**: $7/month
---
## Security Best Practices
### 1. Environment Variables
```bash
# .env
JWT_SECRET=your-secret-key
DATABASE_URL=postgresql://...
ALLOWED_ORIGINS=https://dewe.dev,http://localhost:3001
```
### 2. Rate Limiting
```javascript
const rateLimit = require('express-rate-limit');
const limiter = rateLimit({
windowMs: 15 * 60 * 1000, // 15 minutes
max: 100 // limit each IP to 100 requests per windowMs
});
app.use('/api/', limiter);
```
### 3. Input Validation
```javascript
const { body, validationResult } = require('express-validator');
app.post('/api/proxy', [
body('url').isURL(),
body('method').isIn(['GET', 'POST', 'PUT', 'DELETE', 'PATCH']),
], async (req, res) => {
const errors = validationResult(req);
if (!errors.isEmpty()) {
return res.status(400).json({ errors: errors.array() });
}
// ... rest of code
});
```
---
## Summary
### Current State (Frontend Only):
✅ Works with public APIs
❌ Fails with CORS-protected APIs
❌ Can't secure API keys
❌ No PRO user management
### With Backend:
✅ Works with any API (no CORS issues)
✅ Secure API key storage
✅ PRO user authentication
✅ Rate limiting & caching
✅ Analytics & logging
✅ Production-ready
### Recommendation:
**Start with Option 1 (Simple Proxy)** for immediate CORS bypass, then gradually add authentication and PRO features in Phase 2-3.
**Estimated Timeline:** 2-4 weeks for full implementation with PRO features.