@magicbell/react-headless@5.0.0

Major Changes

• #361 e5027a8 Thanks @smeijer! - Breaking Change!

  We've renamed the categories property to category and the topics property to topic, to reflect that these properties only support a single value. We haven't been supporting multiple categories or topics for a while now, and believe that renaming this property is the right thing to do. It requires a small change on your end, but the clear naming reduces the number of potential bugs caused by misunderstanding.

  If you make use of different stores or filters using the categories or topics properties, you'll need to rename them to their singular variants.

  import { MagicBellProvider } from '@magicbell/react-headless';
  
  const stores = [
    { id: 'default', defaultQueryParams: {} },
    { id: 'unread', defaultQueryParams: { read: false } },
  - { id: 'billing', defaultQueryParams: { categories: ['billing'] } },
  + { id: 'billing', defaultQueryParams: { category: 'billing' } },
  - { id: 'support', defaultQueryParams: { topics: ['support'] } },
  + { id: 'support', defaultQueryParams: { topic: 'support' } },
  ];
  
  export default function Index({ children }) {
    return (
      <MagicBellProvider
        apiKey="__MAGICBELL_API_KEY__"
        userEmail="__MAGICBELL_USER_EMAIL__"
        userKey="__MAGICBELL_USER_KEY__"
        stores={stores}
      >
        {children}
      </MagicBell>
    );
  }

Patch Changes

• Updated dependencies [95bd18d, 13e54bc, 39832a3, e5027a8]:
  • magicbell@4.0.0

@magicbell/project-client@0.2.0

Minor Changes

• #363 036278a Thanks @smeijer! - use fetch as http client

• #358 726be74 Thanks @smeijer! - An early release of @magicbell/project-client, a project/admin facing client, to be used on the server, focussing on the MagicBell v2 API.

Patch Changes

• #362 8f20ec9 Thanks @smeijer! - fix package.json#exports

@magicbell/magicbell-react@11.0.0

Major Changes

• #361 e5027a8 Thanks @smeijer! - Breaking Change!

  We've renamed the categories property to category and the topics property to topic, to reflect that these properties only support a single value. We haven't been supporting multiple categories or topics for a while now, and believe that renaming this property is the right thing to do. It requires a small change on your end, but the clear naming reduces the number of potential bugs caused by misunderstanding.

  If you make use of different stores or tabs using the categories or topics properties, you'll need to rename them to their singular variants.

  import MagicBell, { FloatingNotificationInbox } from '@magicbell/magicbell-react';
  import React from 'react';
  
  const stores = [
    { id: 'default', defaultQueryParams: {} },
    { id: 'unread', defaultQueryParams: { read: false } },
  - { id: 'billing', defaultQueryParams: { categories: ['billing'] } },
  + { id: 'billing', defaultQueryParams: { category: 'billing' } },
  - { id: 'support', defaultQueryParams: { topics: ['support'] } },
  + { id: 'support', defaultQueryParams: { topic: 'support' } },
  ];
  
  const tabs = [
    { storeId: 'default', label: 'Latest' },
    { storeId: 'unread', label: 'Archive' },
    { storeId: 'billing', label: 'Billing' },
    { storeId: 'support', label: 'Issues' },
  ];
  
  export default function Index() {
    return (
      <MagicBell
        apiKey="__MAGICBELL_API_KEY__"
        userEmail="__MAGICBELL_USER_EMAIL__"
        userKey="__MAGICBELL_USER_KEY__"
        stores={stores}
      >
        {(props) => <FloatingNotificationInbox height={450} tabs={tabs} {...props} />}
      </MagicBell>
    );
  }

Patch Changes

• Updated dependencies [e5027a8]:
  • @magicbell/react-headless@5.0.0

@magicbell/in-app@0.2.2

Patch Changes

• #357 139cbb0 Thanks @smeijer! - updated to use new @magicbell/user-client version

• Updated dependencies [139cbb0, 036278a, 8f20ec9]:

  • @magicbell/user-client@0.3.0

@magicbell/embeddable@3.3.28

Patch Changes

• Updated dependencies [e5027a8]:
  • @magicbell/magicbell-react@11.0.0

@magicbell/cli@4.0.0

Major Changes

• #299 df2c87f Thanks @smeijer! - Breaking Change!

  We've renamed the categories property to category and the topics property to topic, to reflect that these properties only support a single value. We haven't been supporting multiple categories or topics for a while now, and believe that renaming this property is the right thing to do. It requires a small change on your end, but the clear naming reduces the number of potential bugs caused by misunderstanding.

  If you make use of the categories or topics filters on magicbell user notifications, you'll need to rename them to their singular variants.

  - magicbell user notifications list --topics support
  + magicbell user notifications list --topic support
  
  - magicbell user notifications mark-all-read --topics billing
  + magicbell user notifications mark-all-read --topic billing
  
  - magicbell user notifications mark-all-seen --topics other
  + magicbell user notifications mark-all-seen --topic other

Minor Changes

• #360 95bd18d Thanks @smeijer! - Auth tokens are now prioritized over api keys.

• #349 13e54bc Thanks @smeijer! - define more notification delivery statuses, added skipped, dropped, failed, and delivered.

Patch Changes

• #348 39832a3 Thanks @smeijer! - removed function to delete push subscriptions, as it doesn't exist on our v1 (current) api.

• Updated dependencies [95bd18d, 13e54bc, 39832a3, e5027a8]:

  • magicbell@4.0.0

@magicbell/magicbell-react@10.11.8

Patch Changes

• 604cce2 Thanks @renovate[bot]! - Updated dependencies:

  • updated @babel/core to ^7.25.2.

@magicbell/in-app@0.2.1

Patch Changes

• ec38aee Thanks @renovate[bot]! - Updated dependencies:

  • updated lit to ^3.2.0.

• #338 640c42c Thanks @renovate! - Updated dependencies:

  • updated @custom-elements-manifest/analyzer to ^0.10.3.

@magicbell/embeddable@3.3.27

Patch Changes

• Updated dependencies [604cce2]:
  • @magicbell/magicbell-react@10.11.8

@magicbell/cli@3.6.1

Patch Changes

• #343 c876c93 Thanks @smeijer! - ensure all native node modules are excluded from the bundle