Web SDK 6 Migration Guide

This page covers the Web package migration from SDK 5.17.x to SDK 6.0.0-beta11.

What changed in SDK 6

• Update the Web package version to 6.0.0-beta11.
• The documented document scanning entry point remains scanWithConfiguration(...).
• The native and wrapper barcode/error-code migrations do not introduce a documented Web application API change.
• Private or undocumented Web API usage may still require a separate comparison with the SDK 6 package API.

Update the package

Update @thegrizzlylabs/web-geniusscan-sdk to 6.0.0-beta11.

npm install @thegrizzlylabs/web-geniusscan-sdk@6.0.0-beta11

or update package.json directly:

{
  "dependencies": {
    "@thegrizzlylabs/web-geniusscan-sdk": "6.0.0-beta11"
  }
}

Document scanning

Keep using scanWithConfiguration(...) for document scanning.

If your app still uses the deprecated scanDocument(...) helper, it is not a required SDK 6 migration item, but new code should prefer scanWithConfiguration(...) because it exposes the full scan result and multi-page document output.

For the complete configuration surface, see the @thegrizzlylabs/web-geniusscan-sdk package documentation.

Error handling

The Web SDK does not expose the native and wrapper scan-flow string-code taxonomy. Keep handling rejected promises as JavaScript errors.

If your Web integration distinguishes license failures, continue to handle the Web SDK license error types and regular Error objects. If your integration uses private Web APIs, compare them with the SDK 6 package API before shipping the migration.

Final checks

After the package update, run the same scan scenarios your SDK 5 integration already covered:

• SDK initialization and license configuration.
• Single-page scan.
• Multi-page scan, if used.
• PDF generation, if used.
• Any custom error handling around rejected scan promises.