magicbell-js

Minor Changes

• #384 6900feb Thanks @smeijer! - fix cjs/esm dual module support

Patch Changes

• Updated dependencies []:
  • @magicbell/[email protected]

Patch Changes

• Updated dependencies [71815e7]:
  • [email protected]

Patch Changes

• Updated dependencies []:
  • @magicbell/[email protected]

Minor Changes

• #378 4e28dba Thanks @smeijer! - fix cjs/esm dual module support

Minor Changes

• #376 71815e7 Thanks @smeijer! - publish proper cjs and esm type definitions

Patch Changes

• Updated dependencies [6900feb]:
  • @magicbell/[email protected]

Patch Changes

• Updated dependencies [71815e7]:
  • [email protected]

Patch Changes

• #370 f8e51c3 Thanks @smeijer! - return categories and category channels from useNotificationPreferences hook in stable order

Patch Changes

• #370 f8e51c3 Thanks @smeijer! - maintain order of categories and channels when updating notification preferences

• #371 8e08182 Thanks @smeijer! - make sure that last category in notification preferences can be scrolled to

• Updated dependencies [f8e51c3]:

  • @magicbell/[email protected]

Patch Changes

• #371 8e08182 Thanks @smeijer! - make sure that last category in notification preferences can be scrolled to

• Updated dependencies [f8e51c3, 8e08182]:

  • @magicbell/[email protected]

Minor Changes

• #357 139cbb0 Thanks @smeijer! - regenerated using liblab v2

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

Patch Changes

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

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]:
  • [email protected]

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/[email protected]

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

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 use topics or categories filters in the UserClient, you'll need to update those params to their singular variant.

  import { UserClient } from 'magicbell/user-client';
  
  const magicbell = new UserClient({
    apiKey: 'your-api-key',
    userEmail: '[email protected]',
  });
  
  const notifications = await magicbell.notifications.list({
  -  categories: ['billing'],
  +  category: 'billing',
  -  topics: ['invoice-1'],
  +  topic: 'invoice-1',
  });
  

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.

Patch Changes

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

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

  • @magicbell/[email protected]

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]:

  • [email protected]

Patch Changes

• Updated dependencies [e5027a8]:
  • @magicbell/[email protected]

Patch Changes

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

  • updated @babel/core to ^7.25.2.