Conflict with @telegram-apps/sdk 3.x

[PeaceeDuck]

When using this package with @telegram-apps/sdk version 3.x in a Nuxt.js project, the following issues occur:

I first installed @telegram-apps/sdk, then analytics
– when trying to initialize analytics, I keep getting an error saying that the project is opened outside of Telegram (even though it is opened inside Telegram).

I tried installing the package in a separate node_modules directory to avoid conflicts. Analytics started working, but the functionality of @telegram-apps/sdk stopped working:
– the back button doesn't work
– the viewport doesn't work

I suspect this is happening because there are two versions of @telegram-apps/sdk, which causes some parts to break.

In the code, @telegram-apps/sdk is used once in
\src\controllers\Session.controller.ts:
import { retrieveLaunchParams } from '@telegram-apps/sdk';

But according to the SDK documentation, to get retrieveLaunchParams, you should use bridge:
https://docs.telegram-mini-apps.com/packages/telegram-apps-bridge/launch-parameters

[PeaceeDuck]

UPD
The functionality has been restored. I'm using the following configuration:
"nuxt": "^3.12.3",
"@telegram-apps/sdk": "3.11.4"
I'm connecting analytics via a <script> tag.

All Telegram functionality works fine except for the invoice.
After opening and closing the invoice, the app remains in a "frozen" state —
as if the status is intercepted by the analytics and doesn't propagate further,
so the SDK can't resolve the promise for the invoice.

I tried disabling the analytics in the code, and after that, the invoice started working properly.

[alpinskiy]

Shall be fixed in version "1.6.4". Please ensure that @telegram-apps/sdk-react get initialized before analytics.