Skip to content

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 1, 2025

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to upcoming, this PR will be updated.

Releases

create-qwik@1.16.1

Patch Changes

  • 🐞🩹 set sideEffects: false to the lib template, otherwise there might be some side effects imports when building a consumer project. (by @gioboa in #7855)

  • 🐞🩹 fix up vscode settings merge. Use JSON5 to parse settings.json to prevent parsing errors. (by @gioboa in #7858)

  • 🛠 use the new version of @croct/json5-parser to merge JSON5 and preserve comments (by @gioboa in #7884)

@builder.io/qwik@1.16.1

Patch Changes

  • 🐞🩹 The entry.ssr renderToStream preloader.preloadProbability option is now deprecated because this could cause performance issues with bundles fetched on click instead of being preloaded ahead of time. (The preloader still relies on probabilities to know preload the most likely bundles first) (by @maiieul in #7847)

  • 🐞🩹 Link prefetch now always preloads Link prefetch bundles on monorepos (by @maiieul in #7835)

  • 🐞🩹 Rollup's hoistTranstiveImports is now set to false because the hoisting added unnecessary bundles to be preloaded to the bundle-graph static imports graph. This could lead to a suboptimal preloading experience. (by @maiieul in #7850)

  • 🛠 Add check-client command to verify bundle freshness (by @JerryWu1234 in #7517)

  • ✨ All qwik packages are now marked as side effect free in their package.json. This should remove a few unecessary empty imports added by rollup and then not tree-shaken like import "./preloader.js". (by @maiieul in #7908)

  • 🐞🩹 unmount qwikify react root alongside with qwik component (by @sashkashishka in #7864)

  • 🐞🩹 preloader now preloads bundles as long as they are part of the current viewport's bundles graph, even if their probability is very small (by @maiieul in #7836)

  • ✨ maxIdlePreloads is now constant over time so you know for sure how many bundles will be preloaded concurrently during idle. (by @maiieul in #7846)

  • 🛠 use patched domino instead of qwik-dom (by @gioboa in #7842)

  • 🐞🩹 Qwik is now smarter at bundling non QRL source files and qwik libraries modules (e.g. helpers, enums, inline components, etc.) together. (by @maiieul in #7888)

@builder.io/qwik-city@1.16.1

Patch Changes

  • 🐞🩹 fix behaviour of checkOrigin: "lax-proto" in createQwikCity (by @asaharan in #7865)

  • 🛠 Add check-client command to verify bundle freshness (by @JerryWu1234 in #7517)

  • 🐞🩹 return 404 with invalid URL. (by @gioboa in #7902)

  • ✨ All qwik packages are now marked as side effect free in their package.json. This should remove a few unecessary empty imports added by rollup and then not tree-shaken like import "./preloader.js". (by @maiieul in #7908)

  • ✨ SPA Link navigation now preloads the next route bundles on click with maximum probability, speeding up SPA navigation. (by @maiieul in #7849)

  • 🐞🩹 Your service-worker.js won't be unregistered anymore if you added custom logic to it. (by @maiieul in #7872)

    Note: Qwik 1.14.0 and above now use <link rel="modulepreload"> by default. If you didn't add custom service-worker logic, you should remove your service-worker.ts file(s) for the ServiceWorkerRegister Component to actually unregister the service-worker.js and delete its related cache. Make sure to keep the ServiceWorkerRegister Component in your app (without any service-worker.ts file) as long as you want to unregister the service-worker.js for your users.

eslint-plugin-qwik@1.16.1

@github-actions github-actions bot requested review from a team as code owners September 1, 2025 11:33
@github-actions github-actions bot force-pushed the changeset-release/upcoming branch from 1e668f5 to a1e65e3 Compare September 2, 2025 08:36
@github-actions github-actions bot force-pushed the changeset-release/upcoming branch from a1e65e3 to d012ad1 Compare September 4, 2025 06:52
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