Skip to content

Update dependency @sveltejs/adapter-static to v1.0.6 - #54

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/sveltejs-adapter-static-1.x
Open

Update dependency @sveltejs/adapter-static to v1.0.6#54
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/sveltejs-adapter-static-1.x

Conversation

@renovate

@renovate renovate Bot commented Apr 5, 2024

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
@sveltejs/adapter-static (source) 1.0.0-next.341.0.6 age confidence

Release Notes

sveltejs/kit (@​sveltejs/adapter-static)

v1.0.6

Compare Source

Patch Changes

v1.0.5

Compare Source

Patch Changes
  • docs: move adapter docs to site (#​8531)

v1.0.4

Compare Source

Patch Changes

v1.0.3

Compare Source

Patch Changes

v1.0.2

Compare Source

Patch Changes
  • docs: clarify that you can build SPAs with adapter-static (#​8502)

v1.0.1

Compare Source

Patch Changes
  • fix: match adapter-vercel logic for serving prerendered content (#​8332)

v1.0.0

Compare Source

Major Changes

First major release, see below for the history of changes that lead up to this.
Starting from now all releases follow semver and changes will be listed as Major/Minor/Patch

v1.0.0-next.50

Compare Source

Patch Changes
  • chore: add peerDependencies, add more specific next version (#​8141)

v1.0.0-next.49

Compare Source

Patch Changes
  • breaking: replace automatic fallback generation with builder.generateFallback(fallback) (#​8013)

v1.0.0-next.48

Compare Source

Patch Changes

v1.0.0-next.47

Compare Source

Patch Changes

v1.0.0-next.46

Compare Source

Patch Changes
  • Make options object optional (#​7341)

v1.0.0-next.45

Compare Source

Patch Changes
  • feat: more info about prerendering errors, add strict option to adapter-static (#​7264)

v1.0.0-next.44

Compare Source

Patch Changes

v1.0.0-next.43

Compare Source

Patch Changes
  • Improve performance by compressing in parallel (#​6710)

v1.0.0-next.42

Compare Source

Patch Changes
  • docs: more specific error message when prerendering fails (#​6577)

v1.0.0-next.41

Compare Source

Patch Changes
  • Better error when encountering not-fully-prerenderable routes (#​6474)

v1.0.0-next.40

Compare Source

Patch Changes
  • breaking: require all routes to be prerenderable when not using fallback option (#​6392)

v1.0.0-next.39

Compare Source

Patch Changes
  • Move compress logic to Builder API (#​5822)

v1.0.0-next.38

Compare Source

Patch Changes
  • breaking: remove writeStatic to align with Vite (#​5618)

v1.0.0-next.37

Compare Source

Patch Changes
  • breaking: Throws when correctly configured to run as a static site of a SPA (#​5562)

v1.0.0-next.36

Compare Source

Patch Changes
  • Remove ENABLE_VC_BUILD check, use v3 build output API for all apps deployed to Vercel (#​5514)

v1.0.0-next.35

Compare Source

Patch Changes
  • chore: upgrade TypeScript to 4.7.4 (#​5414)

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Apr 5, 2024

Copy link
Copy Markdown
Author

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @karma-lies/reset@1.0.1
npm ERR! Found: @sveltejs/kit@1.0.0-next.347
npm ERR! node_modules/@sveltejs/kit
npm ERR!   dev @sveltejs/kit@"1.0.0-next.347" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @sveltejs/kit@"^1.0.0" from @sveltejs/adapter-static@1.0.6
npm ERR! node_modules/@sveltejs/adapter-static
npm ERR!   dev @sveltejs/adapter-static@"1.0.6" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-05T21_07_21_609Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-05T21_07_21_609Z-debug-0.log

@netlify

netlify Bot commented Apr 5, 2024

Copy link
Copy Markdown

Deploy Preview for resetpresents failed.

Name Link
🔨 Latest commit d00f351
🔍 Latest deploy log https://app.netlify.com/sites/resetpresents/deploys/66106815503e340008a1fba5

@renovate

renovate Bot commented Aug 10, 2025

Copy link
Copy Markdown
Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @karma-lies/reset@1.0.1
npm error Found: @sveltejs/kit@1.0.0-next.347
npm error node_modules/@sveltejs/kit
npm error   dev @sveltejs/kit@"1.0.0-next.347" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @sveltejs/kit@"^1.0.0" from @sveltejs/adapter-static@1.0.6
npm error node_modules/@sveltejs/adapter-static
npm error   dev @sveltejs/adapter-static@"1.0.6" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-08-11T23_31_22_216Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-11T23_31_22_216Z-debug-0.log

@renovate renovate Bot changed the title chore(deps): update dependency @sveltejs/adapter-static to v1.0.6 Update dependency @sveltejs/adapter-static to v1.0.6 Apr 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants