Skip to content
This repository has been archived by the owner on Aug 31, 2023. It is now read-only.

Releases: johannschopplich/kirby-vue3-starterkit

v5.2.1

25 Mar 08:02
Compare
Choose a tag to compare

   🚨 Breaking Changes

   🐞 Bug Fixes

    View changes on GitHub

v5.2.0

18 Nov 18:37
Compare
Choose a tag to compare

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub

v5.1.1

02 Sep 12:29
Compare
Choose a tag to compare

   🐞 Bug Fixes

    View changes on GitHub

v5.1.0

25 Aug 06:19
Compare
Choose a tag to compare

   🚀 Features

    View changes on GitHub

5.0.0

16 Aug 14:35
Compare
Choose a tag to compare

This release mainly drops the service worker. The overall setup stayed similar to the v4 release cycle.

Share Dev App on Local Wi-Fi

This new feature developed by @dennisbaum introduces the possibility to access the dev machine in the same (W)LAN by mobile devices while receiving Vite HMR updates. You can configure it by adapting your local .env file.

⚠️ Breaking Changes

The service worker has been removed completely, as it resulted in a more complicated setup and wasn't actively developed anymore. If you prefer to still use the service worker, you can add it manually again by referring to this commit: 5086bd0.

Contributors

4.2.0

23 May 14:15
Compare
Choose a tag to compare

This release includes several new features, as well as overall optimizations and simplifications.

Notable Changes

  • Use <script setup> in every Vue.js component
  • Support draft previews from the Kirby Panel
  • Add a example deploy script for usage with Ploi

Use kirby-extended plugin to generate meta tags

SEO-relevant tags are now handled by kirby-extended.

// /site/config/config.php
// See https://github.com/johannschopplich/kirby-extended/blob/main/docs/meta.md
'kirby-extended' => [
    'meta' => [
        'defaults' => function (\Kirby\Cms\App $kirby, \Kirby\Cms\Site $site, \Kirby\Cms\Page $page) {
            $description = $page->description()->or($site->description())->value();

            return [
                'opengraph' => [
                    'image' => '/img/android-chrome-512x512.png'
                ],
                'twitter' => [
                    'image' => '/img/android-chrome-512x512.png'
                ],
                'jsonld' => [
                    'WebSite' => [
                        'url' => $site->url(),
                        'name' => $site->title()->value(),
                        'description' => $description
                    ]
                ]
            ];
        }
    ]
]

Contributors

4.1.0

19 Oct 15:04
Compare
Choose a tag to compare

Absolute Asset Paths Without Host

By popular request, asset URLs won't be prepended by the host anymore.

<!-- From v4.1.0 onwards -->
<link href="/dist/assets/index.fb4887ac.css" rel="stylesheet">
<script async src="/dist/assets/index.ac45b29f.js" type="module"></script>

4.0.0

19 Oct 06:23
Compare
Choose a tag to compare

On-Demand Components Auto Importing

Components will be automatically imported on-demand thanks to unplugin-vue-components. Thus, no need to import and register your components manually anymore! If you register the parent component asynchronously (or via a lazy route), the auto-imported components will be code-split along with their parent.

The following template will be transpiled by Vite on the fly.

From:

<template>
  <div>
    <Intro>Headline</Intro>
  </div>
</template>

To:

<template>
  <div>
    <Intro>Headline</Intro>
  </div>
</template>

<script>
import Intro from "../components/Intro.vue";

export default {
  components: {
    Intro,
  },
};
</script>

Nuxt-Inspired Module System

Introducing a custom user module system. Every .js file inside the src/modules folder following the template below will be installed automatically.

/** @param {import("vue").App} app */
export const install = (app) => {
  // Do something with `app`, like `app.use`
};

Everything you want to add to the app instance before mounting may be added here. For example, the Vue Router is now a module itself.

Other Notable Changes

  • Upgrade dependencies
  • Remove custom build target and inherit Vite's default.
  • Fix compatibility with PHP 7.4.
  • Let Prettier handle formatting of frontend files.
  • Better Docker support with new KIRBY_MODE environment variable (optional).
  • Minor JSDoc updates, general optimizations, cleanups and more.

3.2.0

20 Mar 09:40
Compare
Choose a tag to compare

⚠️ Potentially breaking changes

  • The following environment variables have been renamed to be more declarative:
    • VITE_ENABLE_SW to VITE_SERVICE_WORKER
    • VITE_ENABLE_SWR to VITE_STALE_WHILE_REVALIDATE
    • KIRBY_DEV_HOSTNAME to KIRBY_DEV_HOSTNAME
    • KIRBY_SERVER_PORT to KIRBY_DEV_PORT

Notable changes

  • Routes have been refactored to unify rendering HTML and JSON content by one function.
  • Add the MIME type to JSON preload requests – if the request doesn't match the given type for any reason, it is skipped
  • Use Kirby's pages cache instead of a namespaced cache bucket, thus on page and site updates Kirby handles flushing the cache, not the plugin itself anymore.
  • Pass the Kirby instance ($kirby) to the index template.
  • Use esbuild for the service worker generation script, thus dropping the terser dependency all along.

3.1.1

14 Mar 18:28
Compare
Choose a tag to compare

Notable changes

  • The page object returned by the usePage() hook is now readonly just like useSite()