Commit activity
Last 12 weeks · 0 commits
Community health
2 of 6 standards met
37
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · 2 in progress · Last activity 2mo ago
See all on GitHub →
I tried to keep Deno Deploy and the still-experimental in mind, but only really hard-codes this default path. Therefore, should be fully backwards compatible. Accept a new object when instantiating the adapter with a single option: . Fully backwards-compatible, defaults to the existing value of . These two have new test cases, both for the Vite-like behaviour and for the custom out-dir functionality. Also hardened the out-dir clean-up by following Vite's model: skip emptying if the resolved path is outside the project root and warn. A utils test covers this. The commit also has the side-effect of updating the lockfile, since the last change to it didn't. Closes #21.
Would be great if the adapter had some manner of termination signal handling in the module. Ideally with proper draining of current requests before closing everything. Both and should be taken into account, optionally with a timeout.
When launching in a custom setup, the adapte ignores and always serves on the Deno-default . Would be great if the command above respected the override.
Recent fixes
Bumps the package version to 0.2.1. The 0.2.0 publish never landed on npm because the NPM_TOKEN secret was unauthorized; the workflow has since been switched to trusted publishing in #19. Cutting 0.2.1 as a fresh version so the new OIDC flow has a clean tag to publish. The content shipped under this version is the same as what 0.2.0 was meant to ship plus the release workflow change itself.
Switches the release workflow from a long-lived NPM_TOKEN secret to npm's trusted publishing flow, where the GitHub Actions runner mints a short-lived OIDC token that npm exchanges for publish credentials. This removes the token rotation burden (the failed v0.2.0 publish was caused by an unauthorized NPM_TOKEN) and produces a signed provenance attestation for each published tarball. Requires the trusted publisher to be configured on npmjs.com for @deno/svelte-adapter pointing at this repository and workflow filename, which has already been done. Node 22's bundled npm is older than the 11.5.1 minimum for OIDC, so the workflow upgrades npm before publishing.
Bumps the package version from 0.1.1 to 0.2.0 in preparation for the next release. Cutting a minor bump to cover the recently merged changes (remote-function CSRF protection, SvelteKit built-in observability support, and static paths with spaces). Once merged, drafting a GitHub Release tagged v0.2.0 will trigger the existing release workflow to publish @deno/svelte-adapter to npm.
Structured data for AI agents
Repository: denoland/svelte-adapter. Description: Deno Deploy SvelteKit adapter Stars: 32, Forks: 4. Primary language: TypeScript. Languages: TypeScript (87.3%), Svelte (10.7%), CSS (1%), JavaScript (0.8%), HTML (0.2%). License: MIT. Latest release: v0.2.1 (2mo ago). Open PRs: 2, open issues: 8. Last activity: 2mo ago. Community health: 37%. Top contributors: marvinhagemeister, afonsograca, bartlomieju, lucacasonato, tolu.