Update dependency @builder.io/qwik to v1.16.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@builder.io/qwik (source)	1.12.1 -> 1.16.0

---

Release Notes

QwikDev/qwik (@​builder.io/qwik)

v1.16.0

Compare Source

Minor Changes

• ✨ bump Vite to v7 (by @​gioboa in #​7762)

Patch Changes

• 🐞🩹 Keeping the service worker components now properly unregisters them. (by @​maiieul in #​7781)

• 🛠 remove a grace period before unregistering events from qwikloader (by @​Varixo in #​7818)

• 🐞🩹 Keeping the service worker components now also removes their associated Cache storage. (by @​maiieul in #​7782)

• 🐞🩹 fix up open in editor feature (by @​LazyClicks in #​7785)

• 🐞🩹 SSR was missing some places with nonce for CSP. Now CSP should work even when strict-dynamic (by @​wmertens in #​7776)

v1.15.0

Compare Source

Minor Changes

• 🐞🩹 the preloader bundle graph file is now built as an asset. This is cleaner and avoids i18n translation of the file. (by @​wmertens in #​7650)

Patch Changes

• 🐞🩹 Use correct working directory for Deno environment (by @​siguici in #​7699)

• ⚡ the qwikloader is no longer embedded in the SSR results. Instead, the same techniques are used as for the preloader to ensure that the qwikloader is active as soon as possible, loaded from a separate bundle. This reduces SSR page size by several kB end ensures that subsequent qwikloader loads are nearly instant. (by @​wmertens in #​7613)

• 🐞🩹 Removed backdrop-filter of vite-error-overlay to prevent perf issues with multiple errors (by @​intellix in #​7676)

• 🐞🩹 assetsDir and debug:true will no longer break your application. (by @​maiieul in #​7638)

• 🐞🩹 We now also output the preloader as .cjs for non esm environments (e.g. jest 29 and below). (by @​maiieul in #​7736)

• 🐞🩹 cypress component tests became slow in 1.9.1. This is now fixed. (by @​maiieul in #​7736)

• ✨ q-manifest.json now also includes the generated assets (by @​wmertens in #​7650)

• 🐞🩹 support q-manifest resolution under Bun runtime (#​7565) (by @​siguici in #​7669)

• 🐞🩹 set correct script type for qwik loader (by @​Varixo in #​7710)

• 🛠 update devDependencies and configurations (by @​JerryWu1234 in #​7695)

v1.14.1

Compare Source

v1.14.0

Compare Source

Minor Changes

• ✨ Major improvements to prefetching with automatic bundle preloading (by @​wmertens in #​7453)

  • This removes the need for service workers, and instead utilize modulepreload link tags for better browser integration.
  • Improves initial load performance by including dynamic imports in the prefetch
  • Reduces complexity while maintaining similar (and even better) functionality
  • Enables some preloading capabilities in dev mode (SSR result only)
  • Includes path-to-bundle mapping in bundle graph (this improves the experience using the <Link> component, AKA "single page app" mode)
  • Server now has built-in manifest support (so no need to pass manifest around)
  • Moves insights-related build code to insights plugin

  ---

  ⚠️ ATTENTION:

  • Keep your service worker code as is (either <ServiceWorkerRegister/> or <PrefetchServiceWorker/>).
  • Configure your server to provide long caching headers.

  Service Worker:

  This new implementation will use it to uninstall the current service worker to reduce the unnecessary duplication.

  The builtin service workers components are deprecated but still exist for backwards compatibility.

  ⚠️ IMPORTANT: Caching Headers:

  The files under build/ and assets/ are named with their content hash and may therefore be cached indefinitely. Typically you should serve build/* and assets/* with Cache-Control: public, max-age=31536000, immutable.

  However, if you changed the rollup configuration for output filenames, you will have to adjust the caching configuration accordingly.

  ---

  You can configure the preload behavior in your SSR configuration:

  // entry.ssr.ts
  export default function (opts: RenderToStreamOptions) {
    return renderToStream(<Root />, {
      preload: {
        // Enable debug logging for preload operations
        debug: true,
        // Maximum simultaneous preload links
        maxIdlePreloads: 5,
        // Minimum probability threshold for preloading
        preloadProbability: 0.25
        // ...and more, see the type JSDoc on hover
      },
      ...opts,
    });
  }

Optional for legacy apps:

For legacy apps that still need service worker functionality, you can add it back using:

npm run qwik add service-worker

This will add a basic service worker setup that you can customize for specific caching strategies, offline support, or other PWA features beyond just prefetching.

Patch Changes

• 🐞🩹 linting errors which were previously being ignored across the monorepo. (by @​better-salmon in #​7418)

• 🐞🩹 now qwikloader is loaded only once in all cases (by @​wmertens in #​7506)

v1.13.0

Compare Source

Minor Changes

• The useTask# @​builder.io/qwik function's eagerness` option is deprecated and will be removed in version 2. (by @​sreeisalso in #​7345)

Patch Changes

• 🐞🩹 Error boundary ErrorBoundary and fix useErrorBoundary (by @​damianpumar in #​7342)

• 🐞 🩹 The qwik-city ServiceWorkerRegister and qwik PrefetchServiceWorker now prefetch all their qrls to prevent under-prefetching (by @​maiieul in #​7417)

• 🐞🩹 When csr is true, it causes a crash because resolve cannot be null as the second parameter (by @​JerryWu1234 in #​7420)

• updated drizzle to latest version (by @​sreeisalso in #​7288)

• 🐞 fix(rollup): improve manualChunks logic to minimize over-prefetching (by @​maiieul in #​7362)

• ✨ Add the ability to see chunks names in preview/production environments to facilitate debugging of production-only bugs (by @​maiieul in #​7293)

• Emit an CustomEvent qviewTransition when view transition starts. (by @​GrandSchtroumpf in #​7237)

• ✨ Ability to keep using tailwind v3 through the cli (by @​maiieul in #​7403)

• dev server now correctly handles css and js importers, also hmr persistence (by @​thejackshelton in #​7389)

• 🐞🩹 set default value of lint to false to improve the execution performance (by @​JerryWu1234 in #​7425)

• 🐞🩹 manual QRL grouping now works again. This is needed for Insights to work. (by @​wmertens in #​7444)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the @builder.io/qwik dependency from version 1.12.1 to 1.13.0. This involves changes to the package.json and pnpm-lock.yaml files to reflect the new version.

Updated class diagram for @builder.io/qwik

classDiagram
  class Qwik {
    <<package>>
    -version: 1.13.0
  }
  note for Qwik "Updated to version 1.13.0"

Loading

File-Level Changes

Change	Details	Files
Dependency @builder.io/qwik was updated from version 1.12.1 to 1.13.0.	Updated the version of @builder.io/qwik.	pnpm-lock.yaml package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud