Skip to content

Commit 4f9e1a5

Browse files
committed
remove unused code
1 parent bae54bb commit 4f9e1a5

File tree

1 file changed

+1
-82
lines changed

1 file changed

+1
-82
lines changed

apps/svelte.dev/src/routes/packages/packages-meta.ts

Lines changed: 1 addition & 82 deletions
Original file line numberDiff line numberDiff line change
@@ -1,60 +1,5 @@
11
import type { Package } from '$lib/server/content';
22

3-
const TAGS = {
4-
'design-system': {
5-
prompt:
6-
'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, component libraries. 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.'
7-
},
8-
ui: {
9-
prompt:
10-
'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 state management tools or multi-component systems that would qualify as design systems.'
11-
},
12-
router: {
13-
prompt:
14-
'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.'
15-
},
16-
content: {
17-
prompt:
18-
'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.'
19-
},
20-
media: {
21-
prompt:
22-
'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.'
23-
},
24-
server: {
25-
prompt:
26-
'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 or deployment tools (adapter tag).'
27-
},
28-
adapter: {
29-
prompt:
30-
'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.'
31-
},
32-
tooling: {
33-
prompt:
34-
'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.'
35-
},
36-
seo: {
37-
prompt:
38-
'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.'
39-
},
40-
auth: {
41-
prompt:
42-
'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.'
43-
},
44-
integration: {
45-
prompt:
46-
'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.'
47-
},
48-
testing: {
49-
prompt:
50-
"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."
51-
},
52-
miscellaneous: {
53-
prompt:
54-
"Svelte utilities, helpers, and tools that don't fit cleanly into other categories. Examples: state management solutions, custom stores, actions, directives, form validation, performance optimizers, DOM manipulation utilities, scroll utilities, focus managers. Key indicator: provides functionality that enhances Svelte development but doesn't align with existing categories."
55-
}
56-
} satisfies Record<string, { prompt: string }>;
57-
583
const SV_ADD = {
594
packages: [
605
'drizzle-orm',
@@ -67,11 +12,7 @@ const SV_ADD = {
6712
'storybook',
6813
'tailwindcss',
6914
'vitest'
70-
],
71-
alias: {
72-
'@inlang/paraglide-js': 'paraglidejs',
73-
'drizzle-orm': 'drizzle'
74-
}
15+
]
7516
};
7617

7718
const FEATURED: { title: string; packages: string[]; weights?: Record<string, number> }[] = [
@@ -260,26 +201,6 @@ const FEATURED: { title: string; packages: string[]; weights?: Record<string, nu
260201
}
261202
];
262203

263-
const OVERRIDES = new Map<string | RegExp, boolean | number | Partial<Package>>([
264-
['vaul-svelte', true],
265-
['@formkit/auto-animate', -10],
266-
['lucide-svelte', -5],
267-
['sveltekit-flash-message', true],
268-
['sveltekit-rate-limiter', true],
269-
['@astrojs/starlight', true],
270-
['playwright', true],
271-
['vitest', true],
272-
['@inlang/paraglide-js', true],
273-
['phosphor-svelte', true],
274-
['@iconify/tailwind4', true],
275-
['@unocss/preset-icons', true],
276-
['drizzle-orm', true],
277-
['prettier', true],
278-
['storybook', true],
279-
['tailwindcss', true]
280-
// [/@smui\//, true] TODO: This kind of pattern complicates things, not supported yet. Instead focusing on getting smui to add svelte to their deps/peerDeps
281-
]);
282-
283204
const OFFICIAL = [
284205
/^@sveltejs\//,
285206
'prettier-plugin-svelte',
@@ -304,8 +225,6 @@ function is_official(pkg: string): boolean {
304225
}
305226

306227
export const PACKAGES_META = {
307-
TAGS,
308-
OVERRIDES,
309228
is_official,
310229
FEATURED,
311230
SV_ADD

0 commit comments

Comments
 (0)