Skip to content

Releases: wevm/frog

[email protected]

07 Nov 02:07
4fbcc44
Compare
Choose a tag to compare

Patch Changes

  • #518 afbedb0 Thanks @dalechyn! - Fixed an issue where Composer Actions from mobile would not work. Got myself nerdsniped in a wrong direction.

[email protected]

06 Nov 00:57
0fcbd0b
Compare
Choose a tag to compare

Patch Changes

  • #514 f99498d Thanks @dalechyn! - Fixed an issue with incorrect JSON-RPC parameters sent for sendTransaction and signTypedDate for mini-apps. Also fixed and improved communication between the mini-app and the parent.

[email protected]

28 Oct 17:35
9482a09
Compare
Choose a tag to compare

Minor Changes

  • #503 908bed1 Thanks @dalechyn! - Breaking Change: frog/vercel was deleted. If you used handle from this package, import it from frog/next.
    Breaking Change: frog/next no longer exports postComposerCreateCastActionMessage. Use createCast from frog/web.

    Introduced frog/web for client-side related logic in favor of frog/next.
    For backwards compatibility, all the previous exports are kept, but will be
    deprecated in future, except for NextJS related handle function.

    Added functionality for the Mini-App JSON-RPC requests. See more.
    Added createCast, sendTransaction, contractTransaction and signTypedData to frog/web.

[email protected]

03 Oct 13:43
2b8e8ca
Compare
Choose a tag to compare

Patch Changes

  • #495 8201ed3 Thanks @dalechyn! - Bumped hono-og to 0.0.28 which has a fix for constant memory leak issue.

  • #495 8201ed3 Thanks @dalechyn! - Bumped hono-og to the latest version which should solve the memory leak
    issue for those who don't use Vercel as the deployment platform.

[email protected]

27 Sep 00:00
795b01e
Compare
Choose a tag to compare

Patch Changes

  • #491 3581ee6 Thanks @dalechyn! - Bumped hono-og to 0.0.28 which has a fix for constant memory leak issue.

[email protected]

10 Sep 11:19
1475c7e
Compare
Choose a tag to compare

Patch Changes

  • #484 34cfb2a Thanks @dalechyn! - Fixed an issue with parsing Composer Action data when verified is false.

  • #483 84c4330 Thanks @dalechyn! - Fixed an issue where min/max height/width would not handle custom values.

[email protected]

29 Aug 15:13
628178f
Compare
Choose a tag to compare

Patch Changes

  • #478 0f482cd Thanks @dalechyn! - Fixed an issue where getFrameMetadata would return escaped symbols.

[email protected]

22 Aug 23:20
850e8f5
Compare
Choose a tag to compare

Minor Changes

  • #476 4539665 Thanks @dalechyn! - Breaking Change: parent and channelKey are deprecated in ComposerActionMessage

    import { postComposerActionMessage } from 'frog/next'
    
    postComposerActionMessage({
      type: "createCast",
      data: {
        cast: {
          embeds: [/*...*/];
          text: 'Hi';
    -     parent: '0x...'
    -     channelKey: '...'
        };
      };
    })
    import { postComposerCreateCastActionMessage } from 'frog/next'
    
    postComposerCreateCastActionMessage({
      embeds: [/*...*/];
      text: 'Hi';
    - parent: '0x...'
    - channelKey: '...'
    })

    See More.

[email protected]

13 Aug 21:12
d06102f
Compare
Choose a tag to compare

Patch Changes

  • #472 8529049 Thanks @dalechyn! - Fixed an issue where a frame without any fonts passed would crash the render process.

[email protected]

10 Aug 22:38
88f1b89
Compare
Choose a tag to compare

Minor Changes

  • #466 d4899ab Thanks @dalechyn! - Breaking Change: Renamed exported Context type to FrameBaseContext.
    Fixed an issue where frame message was parsed incorrectly and was expecting cast_id in Composer Action Handler.
    Exported previously forgotten types.

Patch Changes

  • #471 24d3bec Thanks @dalechyn! - Fixed an issue where defining fonts in multiple places would override each other. Now all defined fonts are grouped altogether.