Hi @Nikunj Chawla , do you mind showing us the code snippet you used for instrumenting? Thanks!
Hi @Jackson Huang , this is the code snippet I use to initialize my amplitude instance.
I am currently using this on Angular(v16.2.7).
Any help is appreciated, thanks!
import * as amplitude from '@amplitude/analytics-browser';import {sessionReplayPlugin} from '@amplitude/plugin-session-replay-browser';
async initialize(userId?: string){ const sessionReplayTracking = sessionReplayPlugin() await amplitude.add(sessionReplayTracking).promise amplitude.init(environment.amplitude_api_key, userId, { defaultTracking: { sessions: true } });}
@Nikunj Chawla I’m wondering if you maybe have had two analytics-types packages installed somehow that are having a conflict with each other. Can you try
```
rm -rf node_modules/
```
and reinstalling your packages via npm or yarn? Then restart your typescript server and see if the error continues
Hey @Kelly Wallach , I did as you asked, removed the extra analytics-types package from the package.json, removed the node_modules and reinstalled packages using npm. After doing all this I get the same error.
The stack trace says the error is at:
node_modules/@amplitude/plugin-session-replay-browser/lib/esm/session-replay.d.ts:10:5
Hi Nikunj,
Let me check on this internally and get back to you!
Best,
Sydney
P.S. Checkout upcoming events and user meetups on our events page.
Dear Nikunj,
Our Engineers attempted to replicate this issue locally but was unsuccessful. The root cause appears to be a potential mismatch of data types. As we cannot replicate the issue, we are having a hard time finding the root cause.
One possible workaround could be to utilize a `// @ts-ignore` comment on the lines that are affected. While this does not resolve the issue, it can prevent the TypeScript compiler from triggering a failure.
Would you be open to trying that workaround?
Best,
Sydney
P.S. Checkout upcoming events and user meetups on our events page.
I am facing the same issue when I just add import { sessionReplayPlugin } from '@amplitude/plugin-session-replay-browser'; and build my project.
I believe if you can add // @ts-ignore in your package that would resolve the issue
File: node_modules/@amplitude/plugin-session-replay-browser/lib/esm/session-replay.d.ts
import { BrowserClient, BrowserConfig, DestinationPlugin, Event, Result } from '@amplitude/analytics-types';
import { SessionReplayOptions } from './typings/session-replay';
export declare class SessionReplayPlugin implements DestinationPlugin {
name: string;
type: "destination";
clientRemove: BrowserClientt'remove'];
config: BrowserConfig;
options: SessionReplayOptions;
constructor(options?: SessionReplayOptions);
// @ts-ignore
setup(config: BrowserConfig, client?: BrowserClient): Promise<void>;
Hi Arun,
Thanks for letting us know the workaround did not work let me see if there is a better solution!
Best,
Sydney
P.S. Checkout upcoming events and user meetups on our events page.
Hi all,
We are addressing Arun’s case in a separate email. To confirm Nikunj are you still having issues on this case? Or did the last suggestion work for you?
Best,
Sydney
This issue is resolved in latest version.
Hi Arun,
That's great to hear! I will go ahead and close out the ticket, but please let me know if you have any followup questions on this topic.
If you have an unrelated question, please create another ticket. Thank you, and have a great day!
Best,
Audrey
P.S. Checkout upcoming events and user meetups on our events page.
