Val Town Code SearchReturn to Val Town

241
242  // Productivity & Automation
243  { name: "Zapier", url: "https://zapier.com/", category: "Productivity", description: "AI-powered automation platform" },
244  { name: "Make", url: "https://www.make.com/", category: "Productivity", description: "Visual automation platform" },
245  { name: "IFTTT", url: "https://ifttt.com/", category: "Productivity", description: "Simple automation platform" },
282
283  // Data & Analytics
284  { name: "DeepAI", url: "https://deepai.org/", category: "Analytics", description: "AI tools and APIs platform" },
285  { name: "H2O.ai", url: "https://www.h2o.ai/", category: "Analytics", description: "AI and machine learning platform" },
286  { name: "DataRobot", url: "https://www.datarobot.com/", category: "Analytics", description: "Automated machine learning platform" },
301  // Cloud AI Services
302  { name: "Google AI Studio", url: "https://aistudio.google.com/", category: "Cloud AI", description: "Google's AI development platform" },
303  { name: "Video Intelligence API", url: "https://cloud.google.com/video-intelligence", category: "Cloud AI", description: "Google Cloud video analysis API" },
304  { name: "NotebookLM", url: "https://notebooklm.google/", category: "Cloud AI", description: "Google's AI research assistant" },
305  { name: "Translation API Basic", url: "https://cloud.google.com/translate", category: "Cloud AI", description: "Google Cloud translation service" },
306  { name: "Gemini Code Assist", url: "https://cloud.google.com/gemini", category: "Cloud AI", description: "Google's AI coding assistant" },
307  { name: "Gemini for Workspace", url: "https://workspace.google.com/solutions/ai", category: "Cloud AI", description: "AI for Google Workspace" },
314  { name: "AWS Comprehend", url: "https://aws.amazon.com/comprehend/", category: "Cloud AI", description: "Amazon's natural language processing" },
315  { name: "Amazon Lex", url: "https://aws.amazon.com/lex/", category: "Cloud AI", description: "Amazon's conversational AI service" },
316  { name: "Google Cloud Natural Language", url: "https://cloud.google.com/natural-language", category: "Cloud AI", description: "Google's text analysis API" },
317  { name: "Dialogflow", url: "https://cloud.google.com/dialogflow", category: "Cloud AI", description: "Google's conversational AI platform" },
318

1import { useState, useEffect } from "react";
2
3const USER_ENDPOINT = "/api/user";
4
5export function useUser() {

20      SUM(num_images) as total_images
21    FROM ${USAGE_TABLE}
22    WHERE our_api_token = 1
23    GROUP BY user_id, username
24    ORDER BY total_price DESC

1import { useState, useEffect } from "react";
2
3const PROJECT_ENDPOINT = "/api/project";
4const FILES_ENDPOINT = "/api/project-files";
5
6export function useProject(projectId: string, branchId?: string) {

1import { useState, useEffect } from "react";
2
3const ENDPOINT = "/api/projects-loader";
4
5export function useProjects() {

1import { useState, useEffect } from "react";
2
3const ENDPOINT = "/api/create-project";
4
5export function useCreateProject() {

1import { useState, useEffect } from "react";
2
3const ENDPOINT = "/api/create-branch";
4
5export function useCreateBranch(projectId: string) {

17  project,
18  branchId,
19  // anthropicApiKey,
20  // bearerToken,
21  selectedFiles,
39    status,
40  } = useChat({
41    api: "/api/send-message",
42    body: {
43      project,

1import { useState, useEffect } from "react";
2
3const ENDPOINT = "/api/project-branches";
4
5export function useBranches (projectId: string) {

13- Generate code in TypeScript or TSX
14- Add appropriate TypeScript types and interfaces for all data structures
15- Prefer official SDKs or libraries than writing API calls directly
16- Ask the user to supply API or library documentation if you are at all unsure about it
17- **Never bake in secrets into the code** - always use environment variables
18- Include comments explaining complex logic (avoid commenting obvious operations)
23### 1. HTTP Trigger
24
25- Create web APIs and endpoints
26- Handle HTTP requests and responses
27- Example structure:
158- **AI Image:** To inline generate an AI image use: `<img src="https://maxm-imggenurl.web.val.run/the-description-of-your-image" />`
159- **Storage:** DO NOT use the Deno KV module for storage
160- **Browser APIs:** DO NOT use the `alert()`, `prompt()`, or `confirm()` methods
161- **Weather Data:** Use open-meteo for weather data (doesn't require API keys) unless otherwise specified
162- **Error Debugging:** Add `<script src="https://esm.town/v/std/catch"></script>` to HTML to capture client-side errors
163- **Error Handling:** Only use try...catch when there's a clear local resolution; Avoid catches that merely log or return 500s. Let errors bubble up with full context
164- **Environment Variables:** Use `Deno.env.get('keyname')` when you need to, but generally prefer APIs that don't require keys
165- **Imports:** Use `https://esm.sh` for npm and Deno dependencies to ensure compatibility on server and browser
166- **Storage Strategy:** Only use backend storage if explicitly required; prefer simple static client-side sites
200### Backend (Hono) Best Practices
201
202- Hono is the recommended API framework
203- Main entry point should be `backend/index.ts`
204- Do NOT use Hono serveStatic middleware
225  });
226  ```
227- Create RESTful API routes for CRUD operations
228- Always include this snippet at the top-level Hono app to re-throwing errors to see full stack traces:
229  ```ts
262   - For files in the project, use `readFile` helpers
263
2645. **API Design:**
265   - `fetch` handler is the entry point for HTTP vals
266   - Run the Hono app with `export default app.fetch // This is the entry point for HTTP vals`