Commit activity
Last 12 weeks · 6 commits
Community health
2 of 6 standards met
37
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Active · 1 in progress · Last activity 1mo ago
See all on GitHub →
Currently the is hard coded. It would be great if it's configurable, when the adapter is being initialized.
This PR changes how the list of static files is generated. Instead of reading the contents of the directory it reads the list directly from the the manifest file generated by svelte kit. Main reason for this change is that creating the assets list from the contents of the directory misses out on files generated during the build as mentioned in https://github.com/denoland/svelte-adapter/issues/16. This is done by importing the file via its path as the object doesn't expose the manifest itself (or the assets list). I updated the tests to: dynamically create one test per file in , checking that all files are served added an extra file in a subdirectory (which is then tested as mentioned above) added a file to the fixture project, and added a test to check that it is served Marked this PR as draft since I don't think it covers all the cases (e.g. workbox, service worker webmanifest generation), which I'll look into later. Closes https://github.com/denoland/svelte-adapter/issues/16
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: 30, Forks: 3. 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 (1mo ago). Open PRs: 1, open issues: 5. Last activity: 1mo ago. Community health: 37%. Top contributors: marvinhagemeister, afonsograca, bartlomieju, lucacasonato, tolu.