Skip to content

Vue Integration #68

Open
Open

Description

@cstrnt

Description:
Abby should have an integration for Vue (preferrably also Nuxt). This Integration should behave pretty closely to the existing Integrations and have feature parity (see React Docs)

Acceptance Criteria:

  • Must be inside of packages/vue
  • Must be named @tryabby/vue
  • Needs to consume @tryabby/core internally
  • Must be written in Typescript and have the same type quality as React etc
  • needs to have the following functionality
    • useAbby -> a function which returns the user's currently selected variant as well as the onAct method
    • useFeatureFlag -> a function which returns the value of the given feature flag
    • useRemoteConfig -> a function which returns the value of the given feature flag
  • there should be tests for the types and the code

Activity

  1. cstrnt commented on Apr 3, 2024

    @cstrnt
    MemberAuthor

    /bounty 20€

  2. algora-pbc commented on Apr 3, 2024

    @algora-pbc

    💎 $40 bounty • Abby

    Steps to solve:

    1. Start working: Comment /attempt #68 with your implementation plan
    2. Submit work: Create a pull request including /claim #68 in the PR body to claim the bounty
    3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

    ❗ Important guidelines:

    • To claim a bounty, you need to provide a short demo video of your changes in your pull request
    • If anything is unclear, ask for clarification before starting as this will help avoid potential rework
    • Low quality AI PRs will not receive review and will be closed
    • Do not ask to be assigned unless you've contributed before

    Thank you for contributing to tryabby/abby!

    Attempt Started (UTC) Solution Actions
    🟢 @bisgeario Jun 02, 2026, 12:08:54 AM #184 Reward
    🟢 @sutaon Jun 02, 2026, 02:17:38 AM WIP
    🔴 @oliverqx Apr 03, 2024, 03:18:02 PM WIP
    🟢 @feliciien Apr 04, 2024, 08:24:07 PM #141 Reward
    🟢 @godd-ctrl May 04, 2026, 10:23:15 PM #179 Reward
    🔴 @asd55667 Nov 11, 2024, 07:44:21 AM WIP
    🟢 @Iineman2 May 11, 2026, 05:45:28 PM #181 Reward
    🔴 @Harihara04sudhan Feb 13, 2025, 02:47:56 PM WIP
  3. oliverqx commented on Apr 3, 2024

    @oliverqx

    /attempt #68

    ETA: EOD April 5th

    Algora profile Completed bounties Tech Active attempts Options
    @oliverqx 6 bounties from 3 projects
    TypeScript, Python
    Cancel attempt
  4. feliciien commented on Apr 4, 2024

    @feliciien

    /attempt #68

    Algora profile Completed bounties Tech Active attempts Options
    @feliciien 5 bounties from 1 project
    MDX, Rust,
    JavaScript & more
    Cancel attempt
  5. algora-pbc commented on Apr 4, 2024

    @algora-pbc

    Note

    The user @oliverqx is already attempting to complete issue #68 and claim the bounty. We recommend checking in on @oliverqx's progress, and potentially collaborating, before starting a new solution.

  6. oliverqx commented on Apr 4, 2024

    @oliverqx

    would appreciate some grace, as I've already spent a considerable amount of time working on the solution. @cstrnt would it be possible to assign me until the ETA I provided?

  7. cstrnt commented on Apr 5, 2024

    @cstrnt
    MemberAuthor

    @oliverqx sure! It's my first time doing bounties, sorry!

  8. cstrnt commented on Apr 5, 2024

    @cstrnt
    MemberAuthor

    And sorry @feliciien for the confusion

  9. oliverqx commented on Apr 5, 2024

    @oliverqx

    no worries thank you!

  10. algora-pbc commented on Apr 17, 2024

    @algora-pbc

    @oliverqx: Reminder that in 14 days the bounty will become up for grabs, so please submit a pull request before then 🙏

  11. simonorzel26 commented on Apr 18, 2024

    @simonorzel26
    Contributor

    @oliverqx Do you need assistance? If you want to, you can make a PR and I can try to help you out!

  12. 38 remaining items

  13. Aming9303 commented on Nov 1, 2026

    @Aming9303

    /attempt #68

    I am working with Codex (AI-assisted) on an independent @tryabby/vue package using the current @tryabby/core. Main has no packages/vue. I will follow the existing integrations, add reactive Vue composables for variants/onAct, feature flags and typed remote configuration, and test runtime behavior, subscription cleanup and public type inference. I will provide the required short demo and state actual validation limits. Existing competing PRs and their unmerged state are acknowledged; I will not copy their implementation. I have not completed the implementation or earned an award.

  14. CarsonCCHsieh commented on Nov 2, 2026

    @CarsonCCHsieh

    /attempt #68

    I have prepared an independent @tryabby/vue implementation on the current @tryabby/core and am submitting it for review.

    Implementation plan and current scope:

    • Typed createAbby plugin/provider and reactive composables for variants plus onAct, feature flags and remote configuration, retaining the existing core transport.
    • Isolated state per app/provider, in-place core update handling, and subscription/action cleanup.
    • Variant selection after client mount and data readiness; SSR can use supplied initial flag/config data without fetching, tracking or touching browser storage.
    • Runtime, SSR and positive/negative TypeScript tests, a changeset and documentation, including a per-request Nuxt plugin example. This does not include a dedicated Nuxt module or Nuxt app test suite.
    • An original synthetic-data playground and short demo video, with actual validation results and platform limitations documented in the PR.

    The 22 Vue runtime/SSR tests passed on Windows with Node 22.8.0 and pnpm 9.9.0. This contribution was prepared with Codex assistance; no competing Vue PR implementation was copied.

    Demo: https://microusada.com/demos/abby-vue/

    Short walkthrough: https://microusada.com/demos/abby-vue/walkthrough.mp4

  15. Bloders-hub commented on Nov 3, 2026

    @Bloders-hub

    /attempt #68

    Pull Request submitted: #213

    Implementation details:

    • Added @tryabby/vue package in packages/vue consuming @tryabby/core
    • Full type parity with @tryabby/react and @tryabby/svelte
    • Implemented createAbby, useAbby, useFeatureFlag, useFeatureFlags, useRemoteConfig, useRemoteConfigVariables, AbbyProvider, AbbyPlugin, and synchronous helpers
    • Cookie storage persistence with proper expiresInDays forwarding
    • Full Vitest test suite (9/9 tests passing) and TypeScript type tests (tsc --noEmit passing with 0 errors)
    • Clean ESM, CJS, and DTS builds via tsup

    @algora-pbc /claim #68

  16. TassioSales commented on Nov 3, 2026

    @TassioSales

    /attempt #68

  17. mau16ro commented on Nov 5, 2026

    @mau16ro

    /attempt #68

    Propuesta enviada en PR #216 (#216) por @mau16ro

  18. khuxaiphi-stack commented on Nov 6, 2026

    @khuxaiphi-stack

    /attempt #68

  19. jeffrey-graham commented on Nov 7, 2026

    @jeffrey-graham

    /attempt #68

    Submitting PR adding @tryabby/vue Vue 3 composable and provider integration (createAbby, AbbyProvider, useAbby, useFeatureFlag, useRemoteConfig).

  20. DACHDigitalwerk commented on Nov 7, 2026

    @DACHDigitalwerk

    /attempt #68

    Submitted complete @tryabby/vue (Vue 3 & Nuxt 3 SSR) SDK package with 36/36 passing Vitest tests and full SSR isolation in PR #201: #201

  21. ossamartinaaron09-ui commented on Nov 7, 2026

    @ossamartinaaron09-ui

    /attempt #68

    I am implementing the Vue 3 integration package (@tryabby/vue) with useAbby, useFeatureFlag, and useRemoteConfig based on @tryabby/core.

  22. flux-axiom commented on Nov 9, 2026

    @flux-axiom

    /attempt #68
    Submitted PR implementing @tryabby/vue in packages/vue with createAbby, useAbby, useFeatureFlag, useRemoteConfig, AbbyProvider, and Vitest runtime + type tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions