Skip to content

Exit prerelease mode#97

Open
ilfa wants to merge 2 commits into
mainfrom
exit-prerelease
Open

Exit prerelease mode#97
ilfa wants to merge 2 commits into
mainfrom
exit-prerelease

Conversation

@ilfa
Copy link
Copy Markdown
Member

@ilfa ilfa commented May 20, 2026

No description provided.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 20, 2026

Coverage report

St.
Category Percentage Covered / Total
🟡 Statements 74.29% 26/35
🟡 Branches 60% 3/5
🟢 Functions 80% 4/5
🟡 Lines 71.88% 23/32

Test suite run success

6 tests passing in 1 suite.

Report generated by 🧪jest coverage report action from 739ca9e

Show full coverage report
St File % Stmts % Branch % Funcs % Lines Uncovered Line #s
🟡 All files 74.28 60 80 71.87
🔴  src 0 100 100 0
🔴   public-api.ts 0 100 100 0 5-12
🟢  src/lib 92.3 60 100 91.3
🟢   fingerprint.module.ts 100 100 100 100
🟢   fingerprint.service.ts 89.47 60 100 88.88 57,64
🟢   version.ts 100 100 100 100
🟡  src/lib/tokens 66.66 100 0 66.66
🟡   fingerprint-angular-settings-token.ts 66.66 100 0 66.66 7

@github-actions
Copy link
Copy Markdown
Contributor

🚀 Following releases will be created using changesets from this PR:

@fingerprint/angular@3.0.0

Major Changes

  • Introduce Fingerprint Agent API v4.

    New package name is @fingerprint/angular.

    This version removes the dependency on @fingerprintjs/fingerprintjs-pro-spa and uses @fingerprint/agent directly.
    Caching is no longer enabled by default. To enable caching, you must configure it in the startOptions of the module.

    The clearCache method has been removed from the FingerprintService. If you need to clear the cache manually, you should do it by directly interacting with the storage you configured.

    ⚠️This is a breaking change. Caching is no longer enabled by default.

    Why enable caching?

    Caching is essential for:

    • Reducing API usage: By storing visitor data locally, you avoid redundant calls to the Fingerprint API for the same visitor session.
    • Improving performance: Cached data is returned instantly, resulting in a faster user experience.
    • Lowering costs: If caching is not enabled manually after the upgrade, it will result in increased API usage on your Fingerprint Dashboard, which may increase your costs.

    Examples

    Enabling session storage caching

    FingerprintModule.forRoot({
      startOptions: {
        apiKey: 'your-fp-public-api-key',
        cache: {
          storage: 'sessionStorage',
          duration: 'optimize-cost',
        },
      },
    })

    Enabling local storage caching

    FingerprintModule.forRoot({
      startOptions: {
        apiKey: 'your-fp-public-api-key',
        cache: {
          storage: 'localStorage',
        },
      },
    })

    For more information, see the Fingerprint Agent documentation. (77b9ef3)

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants