Rerun

Author: PuruVJ

apps/svelte.dev/scripts/registry/npm.ts

@@ -367,6 +367,8 @@ export interface SearchOptions {
 
 	/** Whether to use the cache of markdown files */
 	skip_cached?: boolean;
+
+	exclude_official?: boolean;
 }
 
 export type StructuredInterimPackage = {
@@ -410,7 +412,8 @@ export async function* stream_search_by_keywords({
 	limit = Infinity,
 	fetch = { package_json: true },
 	batch_size = 10,
-	skip_cached = false
+	skip_cached = false,
+	exclude_official = true
 }: SearchOptions): AsyncGenerator<Map<string, StructuredInterimPackage>> {
 	let total_runs = 0;
 	let collected_packages = new Map<string, StructuredInterimPackage>();
@@ -445,6 +448,7 @@ export async function* stream_search_by_keywords({
 				// Process each package
 				for (const obj of results.objects) {
 					if (skip_cached && (await PackageCache.has(obj.package.name))) continue;
+
 					// Check if we've seen this package before (either in current batch or previous batches)
 					if (all_seen_packages.has(obj.package.name)) {
 						console.log(
@@ -469,7 +473,7 @@ export async function* stream_search_by_keywords({
 					// Skip if we've reached the limit
 					if (total_runs >= limit) break;
 
-					// Exclude 'svelte' and '@sveltejs/kit' package
+					// Exclude 'svelte' and Kit
 					if (obj.package.name === 'svelte' || obj.package.name === '@sveltejs/kit') {
 						continue;
 					}

apps/svelte.dev/scripts/registry/update-registry.ts

@@ -1,4 +1,3 @@
-// Credit for original: Astro team
 import { createOpenRouter } from '@openrouter/ai-sdk-provider';
 import { generateText } from 'ai';
 import dotenv from 'dotenv';
@@ -7,6 +6,7 @@ import path from 'node:path';
 import { fileURLToPath } from 'node:url';
 import glob from 'tiny-glob/sync.js';
 import registry from '../../src/lib/registry.json' with { type: 'json' };
+import type { Package } from '../../src/lib/server/content.js';
 import {
 	fetch_details_for_package,
 	fetch_downloads_for_package,
@@ -19,7 +19,7 @@ import {
 	superfetch,
 	type StructuredInterimPackage
 } from './npm.js';
-import type { Package } from '../../src/lib/server/content.js';
+import { program } from 'commander';
 
 dotenv.config({ path: '.env.local' });
 
@@ -140,7 +140,7 @@ interface ProcessBatchesOptions {
 async function process_batches_through_llm({
 	keywords = ['svelte'],
 	limit = Infinity,
-	batch_size = 25,
+	batch_size = 20,
 	max_retries = 2,
 	retry_count = 0,
 	failed_packages = null
@@ -201,19 +201,23 @@ async function process_batches_through_llm({
 					 - Any package with "-react" suffix
 				
 				3. For INCLUDED packages:
-					 - Assign relevant tags
-					 - Clean up description
+					 - Assign relevant tags based on functionality
+					 - ALWAYS provide a terse description:
+						 - Must be plain text (no markdown, HTML, or special chars)
+						 - Should be 30-80 characters, direct and to the point
+						 - Use simple present tense verbs
+						 - No need for complete sentences; can omit articles
 				
 				OUTPUT FORMAT:
 				Return ONLY a valid JSON object like this:
 				{
 					"package-name-1": {
 						"tags": ["tag1", "tag2"],
-						"description": "Description"
+						"description": "Parse Svelte markup without parsing script or style tags, useful for codemods and tooling."
 					},
 					"package-name-2": {
 						"tags": ["tag1", "tag3"],
-						"description": "Description"
+						"description": "Accessible UI components for Svelte applications."
 					}
 				}
 				
@@ -236,7 +240,7 @@ async function process_batches_through_llm({
 				{
 					"package-name": {
 						"tags": ["tag1", "tag2"],
-						"description": "Clean description"
+						"description": "Terse description"
 					}
 				}
 				
@@ -248,13 +252,29 @@ async function process_batches_through_llm({
 				3. Exclude packages without \`\`\`svelte code examples in README
 				4. ALWAYS exclude "embla-carousel-react" and similar packages
 				
+				DESCRIPTION REQUIREMENTS:
+				For ALL qualifying packages:
+				1. Create terse, direct descriptions (30-80 characters)
+				2. Start with a verb in present tense (Parse, Create, Generate, etc.)
+				3. Focus only on core functionality, omit fluff
+				4. Articles (a, an, the) can be omitted
+				5. Use plain text only - no markdown, HTML, or special characters
+				6. Prioritize brevity over completeness
+				
+				EXAMPLE FORMATS:
+				- "Parse Svelte markup without parsing script tags, useful for codemods."
+				- "Generate type definitions for Svelte components."
+				- "Build forms with validation in Svelte apps."
+				- "Convert Markdown to Svelte components."
+				
 				AVAILABLE TAGS:
 				${JSON.stringify(TAGS_PROMPT)}
 				
 				${JSON.stringify(batch_data)}`,
 					maxRetries: 3,
 					temperature: 0.0 // Absolutely no deviation
 				});
+
 				console.timeEnd(`llm-${batch_id}`);
 
 				// Parse the LLM response
@@ -570,8 +590,12 @@ async function* create_map_batch_generator(
 	}
 }
 
-// const svelte_packages = await process_batches_through_llm();
+const svelte_packages = await process_batches_through_llm();
 
-update_cache_from_npm();
-// update_all_github_stars();
+// update_cache_from_npm();
+await update_all_github_stars();
 // delete_untagged();
+
+// program.name('packages').description('Package to curate the svelte.dev/packages list');
+
+// program.command('update').addArgument({ name: 'github-stars', required: false });

apps/svelte.dev/src/lib/registry.json

@@ -1,67 +1,67 @@
 {
 	"tags": {
 		"component-library": {
-			"prompt": "ANY collection of Svelte components (2 or more). UI kits, design systems, widget collections, form components.",
+			"prompt": "MUST contain 2+ reusable Svelte components designed as a cohesive set with shared design principles. Examples: complete UI kits, design systems, form libraries, widget collections. Key indicator: components are intentionally built to work together, share styling patterns, and serve a unified purpose. NOT a single component or unrelated components bundled together.",
 			"title": "Component Collections & UI Kits"
 		},
 		"ui": {
-			"prompt": "ANY UI-related code for Svelte. Single components, styling utilities, animations, transitions, visual elements, modals, tooltips.",
+			"prompt": "Individual visual Svelte components or styling tools focused on appearance. Examples: standalone UI elements (buttons, modals, dropdowns), animation libraries, transition effects, tooltips. Key indicator: primary purpose is enhancing visual presentation. NOT utility libraries, state management tools, or multi-component systems that would qualify as component libraries.",
 			"title": "UI Components & Elements"
 		},
 		"utility": {
-			"prompt": "ANY helper functionality for Svelte. Stores, actions, directives, hooks, form handling, data fetching, validation, i18n.",
+			"prompt": "Non-visual logic and helper functions for Svelte. Examples: custom stores, actions, directives, form validation, state management tools. Key indicator: focuses on behavior and functionality rather than appearance. NOT visual components, routers, or content rendering tools. Solves specific developer implementation challenges with minimal UI output.",
 			"title": "Svelte Utility Helpers"
 		},
 		"router": {
-			"prompt": "ANY routing or navigation related code. Page transitions, route management, URL handling, history management.",
+			"prompt": "Manages navigation and URL handling in Svelte apps. Examples: client-side routers, path matching utilities, navigation guards, route parameter parsers. Key indicator: primary purpose is handling application navigation flow and URL state. NOT page transition animations (ui tag) or general application state management (utility tag).",
 			"title": "Routing & Navigation"
 		},
 		"content": {
-			"prompt": "ANY content or data handling. Markdown, MDX, CMS integration, blogs, static site generation, content editing.",
+			"prompt": "Tools for creating, processing, and rendering structured content in Svelte. Examples: Markdown/MDX processors, CMS connectors, blog frameworks, documentation generators. Key indicator: focused on content authoring, organization, or display. NOT general data fetching (server tag) or UI components (ui tag) unless specifically content-oriented.",
 			"title": "Content Management"
 		},
 		"media": {
-			"prompt": "ANY media-related features. Images, videos, audio, file uploads, media players, carousels, galleries.",
+			"prompt": "Tools specifically for handling images, video, audio or file assets in Svelte. Examples: media players, image galleries, file uploaders, lazy-loading media components. Key indicator: primarily works with media files or streams. NOT general UI components or data fetching utilities unless media-specific.",
 			"title": "Media Handling"
 		},
 		"server": {
-			"prompt": "ANY server-related functionality. SSR, API integration, data fetching, backend communication, cookies, sessions.",
+			"prompt": "Tools for server-side operations and client-server communication in Svelte. Examples: SSR utilities, API clients, data fetching libraries, server action wrappers. Key indicator: facilitates interaction between frontend and backend. NOT client-side state management (utility tag) or deployment tools (adapter tag).",
 			"title": "Server Integration"
 		},
 		"adapter": {
-			"prompt": "ANY SvelteKit deployment solutions. Hosting integrations, platform adapters, deployment utilities.",
+			"prompt": "SvelteKit-specific deployment adapters or hosting integration tools. Examples: platform adapters (Vercel, Netlify, etc.), serverless deployment helpers, hosting configuration utilities. Key indicator: primary purpose is facilitating deployment to specific environments. NOT general server utilities or build tools.",
 			"title": "Deployment Adapters"
 		},
 		"tooling": {
-			"prompt": "ANY development tools. Build plugins, code generation, testing, debugging, development workflows, CLI tools.",
+			"prompt": "Development tools for Svelte that operate outside runtime code. Examples: build plugins, code generators, debugging utilities, CLI tools, linters. Key indicator: used during development process but not part of runtime application code. NOT runtime libraries, components, or server integrations.",
 			"title": "Development Tools"
 		},
 		"preprocessor": {
-			"prompt": "ANY compile-time functionality. Language integration (SCSS/TS), template processing, code transformation.",
+			"prompt": "Compile-time extensions or transformations for Svelte. Examples: language integrations (TypeScript, SCSS), template preprocessors, code transformation tools. Key indicator: modifies or enhances the Svelte compilation process. NOT runtime utilities, components, or post-build optimizations.",
 			"title": "Compile-time Solutions"
 		},
 		"performance": {
-			"prompt": "ANY performance optimization. Bundle optimization, runtime improvements, rendering optimization, lazy loading.",
+			"prompt": "Tools specifically focused on optimizing Svelte application performance. Examples: bundle optimizers, rendering enhancers, code-splitting utilities, memory management tools. Key indicator: primary purpose is improving speed or resource efficiency. NOT general utilities or UI components unless specifically focused on performance optimization.",
 			"title": "Performance Optimizers"
 		},
 		"seo": {
-			"prompt": "ANY SEO-related features. Meta tags, structured data, sitemaps, SEO analysis, head management.",
+			"prompt": "Tools for improving search engine optimization in Svelte applications. Examples: meta tag managers, structured data generators, sitemap creators, link analyzers. Key indicator: primarily concerned with search engine visibility. NOT general head management or routing unless specifically SEO-focused.",
 			"title": "SEO Utilities"
 		},
 		"dom": {
-			"prompt": "ANY direct DOM interaction. Portal components, element queries, viewport detection, scroll handling, focus management.",
+			"prompt": "Low-level tools for direct DOM manipulation in Svelte. Examples: portal components, intersection observers, focus managers, scroll utilities. Key indicator: involves direct interaction with browser DOM outside Svelte's normal element handling. NOT high-level UI components or general utilities that don't require direct DOM access.",
 			"title": "DOM Manipulation"
 		},
 		"auth": {
-			"prompt": "ANY authentication or authorization. Login systems, OAuth, JWT, permission management, user sessions.",
+			"prompt": "User authentication and authorization solutions for Svelte. Examples: login systems, OAuth implementations, JWT handlers, permission managers. Key indicator: primarily concerned with user identity and access control. NOT general API clients or state management unless specifically auth-focused.",
 			"title": "Authentication Solutions"
 		},
 		"integration": {
-			"prompt": "ANY integration with external services or libraries. Database connectors, API clients, third-party service integration.",
+			"prompt": "Connectors between Svelte and external services or systems. Examples: database clients, third-party API wrappers, payment processor integrations. Key indicator: primary purpose is connecting Svelte apps with external platforms. NOT general UI components or utilities unless they specifically bridge to external services.",
 			"title": "External Integrations"
 		},
 		"testing": {
-			"prompt": "Testing utilities, frameworks, or helpers specifically for Svelte applications. Includes test runners, mocking tools, assertion libraries, UI testing, and component testing for Svelte.",
+			"prompt": "Specialized testing tools designed for Svelte applications. Examples: component testing libraries, Svelte-aware test runners, store mocking utilities. Key indicator: explicitly built for testing Svelte code with awareness of Svelte's features. NOT general JavaScript testing tools that aren't Svelte-specific.",
 			"title": "Testing Frameworks"
 		}
 	},

apps/svelte.dev/src/lib/server/generated/registry/0mn1-svelte-adapter-appengine.md

@@ -1,6 +1,6 @@
 ---
 name: "@0mn1/svelte-adapter-appengine"
-description: "Adapter for Svelte that integrates with Google Cloud Appengine"
+description: "Deploy SvelteKit apps to Google Cloud App Engine."
 repo_url: "https://github.com/halfdanj/svelte-adapter-appengine"
 author: "Jonas Jongejan"
 homepage: "https://github.com/halfdanj/svelte-adapter-appengine#readme"
@@ -9,4 +9,5 @@ updated: "2022-06-02T17:02:30.869Z"
 github_stars: 69
 tags: 
   - adapter
+  - server
 ---

apps/svelte.dev/src/lib/server/generated/registry/0xclearview-svelte-tiny-virtual-table.md

@@ -1,10 +1,10 @@
 ---
 name: "@0xclearview/svelte-tiny-virtual-table"
-description: "A tiny but mighty list virtualization component for svelte, with zero dependencies 💪"
+description: "Implement tiny virtual table component for Svelte with zero dependencies."
 repo_url: "https://github.com/0xclearview/svelte-tiny-virtual-table"
 author: "Marcos Gutiérrez"
 homepage: "https://github.com/0xclearview/svelte-tiny-virtual-table#readme"
-downloads: 9
+downloads: 6
 updated: "2024-11-16T13:11:37.125Z"
 tags: 
   - ui

apps/svelte.dev/src/lib/server/generated/registry/0xmageia-mdsvex.md

@@ -0,0 +1,12 @@
+---
+name: "@0xmageia/mdsvex"
+description: "Process Markdown with Svelte components using MDsveX."
+repo_url: "https://github.com/0xmageia/MDsveX"
+author: "pngwn"
+homepage: "https://github.com/0xmageia/MDsveX#readme"
+downloads: 1
+updated: "2023-10-08T01:00:50.441Z"
+tags: 
+  - preprocessor
+  - content
+---

apps/svelte.dev/src/lib/server/generated/registry/3--prettier-plugin-svelte.md

@@ -0,0 +1,10 @@
+---
+name: "@3-/prettier-plugin-svelte"
+description: "Format Svelte components using Prettier, including HTML, CSS, and JavaScript."
+author: "i18n-now"
+homepage: "https://github.com/i18n-fork/prettier-plugin-svelte/tree/tmp"
+updated: "2025-02-05T07:26:58.910Z"
+tags: 
+  - tooling
+  - preprocessor
+---

apps/svelte.dev/src/lib/server/generated/registry/3--svelte-preprocess.md

@@ -1,11 +1,12 @@
 ---
 name: "@3-/svelte-preprocess"
-description: "A Svelte preprocessor wrapper with baked-in support for commonly used preprocessors"
+description: "Preprocess Svelte components with support for multiple languages."
 repo_url: "https://github.com/i18n-fork/svelte-preprocess"
 author: "Christian Kaisermann"
 homepage: "https://github.com/i18n-fork/svelte-preprocess#readme"
-downloads: 16
+downloads: 2
 updated: "2024-10-21T06:10:48.516Z"
 tags: 
   - preprocessor
+  - tooling
 ---

apps/svelte.dev/src/lib/server/generated/registry/3xpo-svelte-colour-picker.md

@@ -1,10 +1,10 @@
 ---
 name: "@3xpo/svelte-colour-picker"
-description: "A highly customizable color picker component library"
+description: "Offer highly customizable color picker component for Svelte."
 repo_url: "https://github.com/Exponential-Workload/svelte-colour-picker"
 author: "Maxime Dupont"
 homepage: "https://gh.expo.moe/svelte-colour-picker/"
-downloads: 8
+downloads: 2
 updated: "2024-03-01T19:10:08.365Z"
 tags: 
   - ui

apps/svelte.dev/src/lib/server/generated/registry/3xpo-svelte-slider.md

@@ -1,10 +1,10 @@
 ---
 name: "@3xpo/svelte-slider"
-description: "A highly customizable slider component library"
+description: "Create highly customizable slider component library for Svelte."
 repo_url: "https://github.com/Exponential-Workload/svelte-colour-picker"
 author: "Expo"
 homepage: "https://gh.expo.moe/svelte-slider/"
-downloads: 4
+downloads: 2
 dependents: 1
 updated: "2024-01-04T08:25:23.273Z"
 tags: