GitShow/sveltejs/vite-plugin-svelte
sveltejs

vite-plugin-svelte

Svelte plugin for https://vite.dev

by sveltejs
sveltevitevite-plugin
Star on GitHubForknpm

JavaScript

1.0k stars140 forks47 contributorsActive · 2d agoSince 2021@sveltejs/vite-plugin-svelte@7.1.2MIT

Meet the team

See all 47 on GitHub →
dominikg
dominikg500 contributions
renovate[bot]Bot
renovate[bot]242 contributions
github-actions[bot]Bot
github-actions[bot]130 contributions
bluwy
bluwy84 contributions
benmccann
benmccann16 contributions
teemingc
teemingc15 contributions
Rich-Harris
Rich-Harris5 contributions
fehnomenal
fehnomenal2 contributions

Languages

View on GitHub →
JavaScript57%
TypeScript29.1%
Svelte11.3%
HTML2.5%
SCSS0%
CSS0%

Commit activity

Last 12 weeks · 26 commits

Full graph →

Community health

3 of 6 standards met

Community profile →
62
✓README✓License✓Contributing○Code of Conduct○Issue Template○PR Template

Recent PRs & issues

Active · 8 in progress · Last activity 2d ago
See all on GitHub →
dexvdev
feat(inspector): add a wrapper-chain dropdown to jump to where a component is usedOpenPR

What While the inspector is active, a new key combo — — enters "chain mode": clicking a node opens a dropdown of its wrapper chain, i.e. every ancestor `file:line/__open-in-editoralt-xbutton.svelteel.__svelte_meta.loc.parenttype: 'component'{ file, line, column, componentTag }packages/e2e-tests/inspector-viteApp.svelteCounter.svelteApp.sveltepnpm check:typeseslintprettier --checkinspector-vitedocs/inspector.mdminor` changeset are included.

dexvdev · 3d ago

Recent fixes

View closed PRs →
OrientusPrime
fix(inspector): activate under Vite+ by matching its client module pathMergedPR

Problem With , the Svelte Inspector doesn't activate under Vite+ — holding the toggle key (default Alt+X) does nothing. The same config works under stock Vite. Cause The inspector injects its runtime by appending an import to the dev client module, matched by a path filter in : filter: { id: /vite\/dist\/client\/client\.mjs(?:\?|$)/ } This matches stock Vite's . Vite+ resolves its client to () — the and segments are in the opposite order, so the filter doesn't match and the loader import is never appended. The client module still passes through the transform pipeline under Vite+ (only / exclude it, as in stock Vite), so widening the filter is enough. Change Accept both segment orders: filter: { id: /(?:vite\/dist$)/ } Verification On a SvelteKit app running Vite+, then contains the injected import and the inspector mounts (Alt+X works). Stock Vite still matches via the branch. This looked like the smallest change that covers it, and it held up in testing — but whether to support Vite+, and how, is your call.

OrientusPrime · 6d ago
ocavue
PARSE_ERROR in `<script lang="ts">`ClosedIssue

Describe the bug I get the following error when I run Reproduction URL https://github.com/issueset/svelte-vite-ts-parse-error.git Reproduction Logs System Info

ocavue · 6d ago
Structured data for AI agents

Repository: sveltejs/vite-plugin-svelte. Description: Svelte plugin for https://vite.dev Stars: 1036, Forks: 140. Primary language: JavaScript. Languages: JavaScript (57%), TypeScript (29.1%), Svelte (11.3%), HTML (2.5%), SCSS (0%). License: MIT. Topics: svelte, vite, vite-plugin. Latest release: @sveltejs/vite-plugin-svelte@7.1.2 (1mo ago). Open PRs: 8, open issues: 17. Last activity: 2d ago. Community health: 62%. Top contributors: dominikg, renovate[bot], github-actions[bot], bluwy, benmccann, teemingc, Rich-Harris, fehnomenal, baseballyama, maxlath and others.

·@ofershap

Replace github.com with gitshow.dev