Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 30, 2024

This PR contains the following updates:

Package Change Age Confidence
@astrojs/cloudflare (source) ^11.0.5 -> ^12.0.0 age confidence
@pandacss/dev (source) ^0.47.0 -> ^1.0.0 age confidence
undici (source) ^6.19.8 -> ^7.0.0 age confidence
vite-bundle-analyzer ^0.12.0 -> ^1.0.0 age confidence
wrangler (source) ^3.78.7 -> ^4.0.0 age confidence

Release Notes

withastro/astro (@​astrojs/cloudflare)

v12.6.5

Compare Source

Patch Changes

v12.6.4

Compare Source

Patch Changes

v12.6.3

Compare Source

Patch Changes
  • #​14066 7abde79 Thanks @​alexanderniebuhr! - Refactors the internal solution which powers Astro Sessions when running local development with ˋastro devˋ.

    The adapter now utilizes Cloudflare's local support for Cloudflare KV. This internal change is a drop-in replacement and does not require any change to your projectct code.

    However, you now have the ability to connect to the remote Cloudflare KV Namespace if desired and use production data during local development.

  • Updated dependencies []:

v12.6.2

Compare Source

Patch Changes

v12.6.1

Compare Source

Patch Changes

v12.6.0

Compare Source

Minor Changes
  • #​13837 7cef86f Thanks @​alexanderniebuhr! - Adds new configuration options to allow you to set a custom workerEntryPoint for Cloudflare Workers. This is useful if you want to use features that require handlers (e.g. Durable Objects, Cloudflare Queues, Scheduled Invocations) not supported by the basic generic entry file.

    This feature is not supported when running the Astro dev server. However, you can run astro build followed by either wrangler deploy (to deploy it) or wrangler dev to preview it.

    The following example configures a custom entry file that registers a Durable Object and a queue handler:

    // astro.config.ts
    import cloudflare from '@​astrojs/cloudflare';
    import { defineConfig } from 'astro/config';
    
    export default defineConfig({
      adapter: cloudflare({
        workerEntryPoint: {
          path: 'src/worker.ts',
          namedExports: ['MyDurableObject'],
        },
      }),
    });
    // src/worker.ts
    import type { SSRManifest } from 'astro';
    
    import { App } from 'astro/app';
    import { handle } from '@​astrojs/cloudflare/handler';
    import { DurableObject } from 'cloudflare:workers';
    
    class MyDurableObject extends DurableObject<Env> {
      constructor(ctx: DurableObjectState, env: Env) {
        super(ctx, env);
      }
    }
    
    export function createExports(manifest: SSRManifest) {
      const app = new App(manifest);
      return {
        default: {
          async fetch(request, env, ctx) {
            await env.MY_QUEUE.send('log');
            return handle(manifest, app, request, env, ctx);
          },
          async queue(batch, _env) {
            let messages = JSON.stringify(batch.messages);
            console.log(`consumed from our queue: ${messages}`);
          },
        } satisfies ExportedHandler<Env>,
        MyDurableObject,
      };
    }
Patch Changes

v12.5.5

Compare Source

Patch Changes

v12.5.4

Compare Source

Patch Changes

v12.5.3

Compare Source

Patch Changes

v12.5.2

Compare Source

Patch Changes

v12.5.1

Compare Source

Patch Changes

v12.5.0

Compare Source

Minor Changes
  • #​13527 2fd6a6b Thanks @​ascorbic! - The experimental session API introduced in Astro 5.1 is now stable and ready for production use.

    Sessions are used to store user state between requests for on-demand rendered pages. You can use them to store user data, such as authentication tokens, shopping cart contents, or any other data that needs to persist across requests:

v12.4.1

Compare Source

Patch Changes

v12.4.0

Compare Source

Minor Changes
  • #​13514 a9aafec Thanks @​ascorbic! - Automatically configures Cloudflare KV storage when experimental sessions are enabled

    If the experimental.session flag is enabled when using the Cloudflare adapter, Astro will automatically configure the session storage using the Cloudflare KV driver. You can still manually configure the session storage if you need to use a different driver or want to customize the session storage configuration. If you want to use sessions, you will need to create the KV namespace and declare it in your wrangler config. You can do this using the Wrangler CLI:

    npx wrangler kv namespace create SESSION

    This will log the id of the created namespace. You can then add it to your wrangler.json/wrangler.toml file like this:

    // wrangler.json
    {
      "kv_namespaces": [
        {
          "binding": "SESSION",
          "id": "<your kv namespace id here>",
        },
      ],
    }

    By default it uses the binding name SESSION, but if you want to use a different binding name you can do so by passing the sessionKVBindingName option to the adapter. For example:

    import { defineConfig } from 'astro/config';
    import cloudflare from '@&#8203;astrojs/cloudflare';
    export default defineConfig({
      output: 'server',
      site: `http://example.com`,
      adapter: cloudflare({
        platformProxy: {
          enabled: true,
        },
        sessionKVBindingName: 'MY_SESSION',
      }),
      experimental: {
        session: true,
      },
    });

    See the Cloudflare KV docs for more details on setting up KV namespaces.

    See the experimental session docs for more information on configuring session storage.

Patch Changes

v12.3.1

Compare Source

Patch Changes

v12.3.0

Compare Source

Minor Changes
Patch Changes

v12.2.4

Compare Source

Patch Changes

v12.2.3

Compare Source

Patch Changes

v12.2.2

Patch Changes

v12.2.1

Patch Changes

v12.2.0

Minor Changes
Patch Changes

v12.1.0

Minor Changes
  • #​455 1d4e6fc Thanks @​meyer! - Adds wrangler.jsonc to the default watched config files. If a config file is specified in platformProxy.configPath, that file location is watched instead of the defaults.
Patch Changes

v12.0.1

Patch Changes
  • #​465 70e0054 Thanks @​bluwy! - Fixes setting custom workerd and worker conditions for the ssr environment only

v12.0.0

Major Changes
  • #​367 e02b54a Thanks @​alexanderniebuhr! - Removed support for the Squoosh image service. As the underlying library libsquoosh is no longer maintained, and the image service sees very little usage we have decided to remove it from Astro.

    Our recommendation is to use the base Sharp image service, which is more powerful, faster, and more actively maintained.

    - import { squooshImageService } from "astro/config";
    import { defineConfig } from "astro/config";
    
    export default defineConfig({
    -  image: {
    -    service: squooshImageService()
    -  }
    });

    If you are using this service, and cannot migrate to the base Sharp image service, a third-party extraction of the previous service is available here: https://github.com/Princesseuh/astro-image-service-squoosh

  • #​367 e02b54a Thanks @​alexanderniebuhr! - Deprecates the functionPerRoute option

    This option is now deprecated, and will be removed entirely in Astro v5.0. We suggest removing this option from your configuration as soon as you are able to:

    import { defineConfig } from 'astro/config';
    import vercel from '@&#8203;astrojs/vercel/serverless';
    
    export default defineConfig({
      // ...
      output: 'server',
      adapter: vercel({
    -     functionPerRoute: true,
      }),
    });
  • #​375 e7881f7 Thanks @​Princesseuh! - Updates internal code to works with Astro 5 changes to hybrid rendering. No changes are necessary to your project, apart from using Astro 5

  • #​397 776a266 Thanks @​Princesseuh! - Welcome to the Astro 5 beta! This release has no changes from the latest alpha of this package, but it does bring us one step closer to the final, stable release.

    Starting from this release, no breaking changes will be introduced unless absolutely necessary.

    To learn how to upgrade, check out the Astro v5.0 upgrade guide in our beta docs site.

  • #​451 f248546 Thanks @​ematipico! - Updates esbuild dependency to v0.24.0

  • #​392 3a49eb7 Thanks @​Princesseuh! - Updates internal code for Astro 5 changes. No changes is required to your project, apart from using Astro 5

Patch Changes
chakra-ui/panda (@​pandacss/dev)

v1.1.0

Compare Source

Patch Changes

v1.0.1

Compare Source

Patch Changes

v1.0.0

Compare Source

Major Changes
  • a3bcbea: Stable release of PandaCSS
Style Context

Add createStyleContext function to framework artifacts for React, Preact, Solid, and Vue frameworks

import { sva } from 'styled-system/css'
import { createStyleContext } from 'styled-system/jsx'

const card = sva({
  slots: ['root', 'label'],
  base: {
    root: {
      color: 'red',
      bg: 'red.300',
    },
    label: {
      fontWeight: 'medium',
    },
  },
  variants: {
    size: {
      sm: {
        root: {
          padding: '10px',
        },
      },
      md: {
        root: {
          padding: '20px',
        },
      },
    },
  },
  defaultVariants: {
    size: 'sm',
  },
})

const { withProvider, withContext } = createStyleContext(card)

const CardRoot = withProvider('div', 'root')
const CardLabel = withContext('label', 'label')

Then, use like this:

<CardRoot size="sm">
  <CardLabel>Hello</CardLabel>
</CardRoot>
Patch Changes

v0.54.0

Compare Source

Patch Changes

v0.53.7

Compare Source

Patch Changes

v0.53.6

Compare Source

Patch Changes

v0.53.5

Compare Source

Patch Changes

v0.53.4

Compare Source

Patch Changes

v0.53.3

Compare Source

Patch Changes

v0.53.2

Compare Source

Patch Changes

v0.53.1

Compare Source

Patch Changes

v0.53.0

Compare Source

Patch Changes

v0.52.0

Compare Source

Patch Changes

v0.51.1

Compare Source

Patch Changes
  • 9c1327e: Redesigned the recipe report to be more readable and easier to understand. We simplified the JSX and
    Function columns to be more concise.

    BEFORE

    ╔════════════════════════╤══════════════════════╤═════════╤═══════╤════════════╤═══════════════════╤══════════╗
    ║ Recipe                 │ Variant Combinations │ Usage % │ JSX % │ Function % │ Most Used         │ Found in ║
    ╟────────────────────────┼──────────────────────┼─────────┼───────┼────────────┼───────────────────┼──────────╢
    ║ someRecipe (1 variant) │ 1 / 1                │ 100%    │ 100%  │ 0%         │ size.small        │ 1 file   ║
    ╟────────────────────────┼──────────────────────┼─────────┼───────┼────────────┼───────────────────┼──────────╢
    ║ button (4 variants)    │ 7 / 9                │ 77.78%  │ 63%   │ 38%        │ size.md, size.sm, │ 2 files  ║
    ║                        │                      │         │       │            │ state.focused,    │          ║
    ║                        │                      │         │       │            │ variant.danger,   │          ║
    ║                        │                      │         │       │            │ variant.primary   │          ║
    ╚════════════════════════╧══════════════════════╧═════════╧═══════╧════════════╧═══════════════════╧══════════╝

    AFTER

    ╔════════════════════════╤════════════════╤═══════════════════╤═══════════════════╤══════════╤═══════════╗
    ║ Recipe                 │ Variant values │ Usage %           │ Most used         │ Found in │ Used as   ║
    ╟────────────────────────┼────────────────┼───────────────────┼───────────────────┼──────────┼───────────╢
    ║ someRecipe (1 variant) │ 1 value        │ 100% (1 value)    │ size.small        │ 1 file   │ jsx: 100% ║
    ║                        │                │                   │                   │          │ fn: 0%    ║
    ╟────────────────────────┼────────────────┼───────────────────┼───────────────────┼──────────┼───────────╢
    ║ button (4 variants)    │ 9 values       │ 77.78% (7 values) │ size.md, size.sm, │ 2 files  │ jsx: 63%  ║
    ║                        │                │                   │ state.focused,    │          │ fn: 38%   ║
    ║                        │                │                   │ variant.danger,   │          │           ║
    ║                        │                │                   │ variant.primary   │          │           ║
    ╚════════════════════════╧════════════════╧═══════════════════╧═══════════════════╧══════════╧═══════════╝

v0.51.0

Compare Source

Patch Changes

v0.50.0

Compare Source

Minor Changes
  • fea78c7: Adds support for static analysis of used tokens and recipe variants. It helps to get a birds-eye view of how
    your design system is used and answers the following questions:

    • What tokens are most used?
    • What recipe variants are most used?
    • How many hardcoded values vs tokens do we have?
    panda analyze --scope=<token|recipe>

    Still work in progress but we're excited to get your feedback!

Patch Changes

v0.49.0

Compare Source

Minor Changes
  • 97a0e4d: Add support for animation styles. Animation styles focus solely on animations, allowing you to orchestrate
    animation properties.

    Pairing animation styles with text styles and layer styles can make your styles a lot cleaner.

    Here's an example of this:

    import { defineAnimationStyles } from '@&#8203;pandacss/dev'
    
    export const animationStyles = defineAnimationStyles({
      'slide-fade-in': {
        value: {
          transformOrigin: 'var(--transform-origin)',
          animationDuration: 'fast',
          '&[data-placement^=top]': {
            animationName: 'slide-from-top, fade-in',
          },
          '&[data-placement^=bottom]': {
            animationName: 'slide-from-bottom, fade-in',
          },
          '&[data-placement^=left]': {
            animationName: 'slide-from-left, fade-in',
          },
          '&[data-placement^=right]': {
            animationName: 'slide-from-right, fade-in',
          },
        },
      },
    })

    With that defined, I can use it in my recipe or css like so:

    export const popoverSlotRecipe = defineSlotRecipe({
      slots: anatomy.keys(),
      base: {
        content: {
          _open: {
            animationStyle: 'scale-fade-in',
          },
          _closed: {
            animationStyle: 'scale-fade-out',
          },
        },
      },
    })

    This feature will drive consumers to lean in towards CSS for animations rather than JS. Composing animation names is a
    powerful feature we should encourage consumers to use.

Patch Changes

v0.48.1

Compare Source

Patch Changes

v0.48.0

Compare Source

Patch Changes
nodejs/undici (undici)

v7.15.0

Compare Source

What's C


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 added the deps label Nov 30, 2024
@renovate renovate bot requested a review from a team November 30, 2024 18:45
@renovate renovate bot force-pushed the renovate/main-major-enable-automerge-for-devdependencies branch from c64b221 to 0408f8f Compare December 6, 2024 11:20
@renovate renovate bot changed the title chore(deps): update dependency undici to v7 (main) chore(deps): update enable automerge for devdependencies (main) (major) Dec 6, 2024
@renovate renovate bot force-pushed the renovate/main-major-enable-automerge-for-devdependencies branch from 0408f8f to 007c30a Compare March 16, 2025 13:58
@renovate renovate bot force-pushed the renovate/main-major-enable-automerge-for-devdependencies branch from 007c30a to 1ffd5e9 Compare July 3, 2025 19:09
@renovate renovate bot force-pushed the renovate/main-major-enable-automerge-for-devdependencies branch from 1ffd5e9 to a8e4c7e Compare August 8, 2025 09:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants