Skip to content

Releases: QwikDev/astro

1.0

29 Mar 02:12

Choose a tag to compare

Qwik + Astro 1.0

Qwik + Astro 1.0 brings the project onto the new @qwik.dev/* package scope and updates the integration for Qwik v2, Astro 6, and Vite 7.

This is the biggest update to the project so far, with a new upgrade path for existing users, a more capable CLI, improved client-router support, and stronger platform coverage.

What Changed

  • @qwikdev/astro has moved to @qwik.dev/astro
  • create-qwikdev-astro has moved to @qwik.dev/create-astro
  • Qwik + Astro now targets Qwik v2 and Astro 6
  • The CLI better supports both add and a new upgrade flow
  • The docs now include a dedicated upgrade guide for migrating from v1

Breaking Changes

  • Astro 6+ is now required
  • Qwik v2 is now required
  • The package scope changed from @qwikdev/* to @qwik.dev/*
  • If you use Astro’s <ClientRouter />, you now need to configure clientRouter in the Qwik integration options

@qwik.dev/astro 1.0

Highlights:

  • Updated for Qwik v2, Astro 6, and Vite 7
  • Better ClientRouter support for SPA-style navigation
  • Improved useVisibleTask$ behavior under Astro navigation
  • Automatic Qwik entrypoint scanning
  • Server rendering improvements, including cleaner slot handling
  • Platform test coverage for Node, Netlify, and Vercel

@qwik.dev/create-astro 1.0

API Surface Highlights:

  • New add command for existing Astro projects
  • New upgrade command for migrating from v1
  • Better detection of existing Astro config and JSX framework setup
  • Automatic config rewriting for supported add/upgrade cases
  • Starter Qwik component scaffolding for existing-project installs
  • Six built-in starter templates across runtime and formatter options
  • Support for Astro templates via Astro’s template flow
  • Cross-platform CLI testing on Linux, macOS, and Windows

Quick Start

Create a new project:

npm create @qwik.dev/astro@latest

Upgrade an existing v1 project:

npm create @qwik.dev/astro@latest upgrade

Upgrade Guide

If you’re coming from v1, start here:

https://astro.qwik.dev/docs/upgrade/

@qwikdev/create-astro@0.2.3

04 Feb 20:14
9612ea3

Choose a tag to compare

Patch Changes

  • 01db52b: Fix unresolved module handling and update build tooling

    Fixes

    • Return null instead of throwing on unresolved modules in resolveId

    Chore

    • Migrate build tooling from tsup to tsdown

@qwikdev/astro@0.8.3

04 Feb 20:15
9612ea3

Choose a tag to compare

Patch Changes

  • 01db52b: Fix unresolved module handling and update build tooling

    Fixes

    • Return null instead of throwing on unresolved modules in resolveId

    Chore

    • Migrate build tooling from tsup to tsdown

@qwikdev/astro@0.8.2

04 Aug 18:14
08402f1

Choose a tag to compare

Patch Changes

  • 2af2e4a: feat: support global config for renderOpts

    You can now pass the renderOpts option to the qwik integration to set global render options for all Qwik components.

    For example, let's say we wanted to change the base URL for all Qwik build assets on every component used in an Astro file.

    import { defineConfig } from "astro/config";
    import qwik from "@qwikdev/astro";
    
    export default defineConfig({
      integrations: [
        qwik({ include: "**/qwik/*", renderOpts: { base: "my-cdn-url/build" } }),
      ],
    });

@qwikdev/astro@0.8.1

29 Jul 19:30
d51dded

Choose a tag to compare

Patch Changes

  • 7d7b656: feat: Support Qwik Render Options at runtime on a per-component basis.

    This is useful for scenarios where you want to render a Qwik component in an Astro page, but you want to use a different base URL for the Qwik component, or another configuration.

    For example, if you want to render a Qwik component in an Astro page, but you want to use a different base URL for the Qwik component, you can pass the renderOpts prop to the Qwik component.

    <NativeCounter initial={2} renderOpts={{ base: "http://0.0.0.0:4321/build" }} />

    Make sure to import the RenderOptions type from @builder.io/qwik/server and pass it to the component for type safety.

    Want to make a change for all components? Create a global object config and pass it to each component.

@qwikdev/create-astro@0.2.2

11 Jun 13:45
dcb04ef

Choose a tag to compare

Patch Changes

@qwikdev/create-astro@0.2.1

22 May 22:04
b9d19db

Choose a tag to compare

Patch Changes

  • 6fe70b5: feat: update stub versions

@qwikdev/create-astro@0.2.0

22 May 21:14
bff089b

Choose a tag to compare

Minor Changes

  • 823ff01: 🚀 Qwik Astro now supports the Qwik preloader! ⚡️

    ✨ Simplified loader mechanism
    🔄 Improved deployment support
    ⚙️ Enhanced Astro actions integration

    Read more in the upcoming blog post on the Qwik site.

@qwikdev/astro@0.8.0

22 May 21:14
bff089b

Choose a tag to compare

Minor Changes

  • 823ff01: 🚀 Qwik Astro now supports the Qwik preloader! ⚡️

    ✨ Simplified loader mechanism
    🔄 Improved deployment support
    ⚙️ Enhanced Astro actions integration

    Read more in the upcoming blog post on the Qwik site.

@qwikdev/astro@0.7.12

15 Apr 19:33
e709a4e

Choose a tag to compare

Patch Changes

  • bcf04d0: - Fix Vercel builds failing force create serverchunks directory if needed
    • Fix Vercel Adapter Client Static Files Handling