It's not imported, so it wasn't being bundled.

* update watchrtc-sdk version to 1.38.2

* remove persistentEnd call to fix ws socket connect/disconnect when conducting consecutive calls.

Co-authored-by: Subham Sinha <shubham.sinha@spearline.com>

this moves the determination of the git commit to webpack-shared-config
LIB_JITSI_MEET_COMMIT_HASH is still kept for backward compatibility

fix(build) in case git fails use development

* fix(RTC): Remove support for plan-b SDP.
Since unified plan mode becomes the default mode, so does multi-stream mode.

* squash: Remove plan-b unit tests and fix comments

* squash: address review comments

The generated dts file is slightly broken, and breaks upstream projects:

```
> jitsi-meet@0.0.0 tsc:native
> tsc --noEmit --project tsconfig.native.json

node_modules/lib-jitsi-meet/types/index.d.ts:3120:20 - error TS1005: '(' expected.

3120         constructor: typeof JitsiTrackError;
                        ~

node_modules/lib-jitsi-meet/types/index.d.ts:13832:20 - error TS1005: '(' expected.

13832         constructor: typeof JitsiConference;
                         ~
```

* fix(events): unify events to a single EventManager type, add support for single typescript declaration

* fix(lint): fix lint

* fix(events): fix incorrect instatiation

* fix(events): clean up redundant methods

* fix(events): keep EventEmitter name, alias NodeEventEmitter

* fix(events): fix loose reference

* fix(EventEmitter): remove on/off alias as redundant

* fix(RTCUtils): bring event handlers under class to use same event emitter

* fix(RTCUtils): fix lint

* Added rtcstats

* increased webpack performance size warning to 830K

* Addressed most of Saghuls and Andrei's review comments.

* moved rtcstatsUseLibJitsi from analytics to testing

* refactor ljm rtcstats, use ljm conference events

* remove debug logs

* remove wrongly named files

* rename rtcstats module

* fix test

* address code review

* fix pack error

* address code review

---------

Co-authored-by: Nils Ohlmeier <github@ohlmeier.org>

It's the same as async, but with ESM which is more bundle friendly.

For more info: https://github.com/strophe/strophejs/pull/465

https://github.com/strophe/strophejs/pull/603

b42f961f14

Bumps [webpack](https://github.com/webpack/webpack) from 5.57.1 to 5.76.0.
- [Release notes](https://github.com/webpack/webpack/releases)
- [Commits](https://github.com/webpack/webpack/compare/v5.57.1...v5.76.0)

---
updated-dependencies:
- dependency-name: webpack
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>

Update notes:

- The base64-sha1 code got stripped out, so we bundle it now
- There are 2 optional dependencies which we want to ignore to avoid
  extra bundle size: xmldom and ws (the former is used by RN but we
  provide it in the app and the latter is only used by Node
  environments)

A bosh only optimization which is no longer used and does not bring any significant value when measured.

Yarn v2 is a little more picky about what protocols it accepts. npm can
infer we're talking about a GitHub package while the true protocol is
`git+https`, but Yarn v2 wants us to be explicit.

This blocked apps that manage dependencies with Yarn v2 from installing
`lib-jitsi-meet`.

Avoid needing an external dependency.

fix up test failure by including extends Listenable

and update other test dependencies

Do this even if the browser provides a non '-' string for streamId since we rely on this to generate the source name.

We do not want the client to re-use the inactive transceivers that are associated with m-lines for removed remote tracks. Rejecting a m-line on source-remove clears it from the list of available transceivers.

This makes sure we don't leave stray files behind if source JS files are removed.

Bumps [karma](https://github.com/karma-runner/karma) from 6.3.14 to 6.3.16.
- [Release notes](https://github.com/karma-runner/karma/releases)
- [Changelog](https://github.com/karma-runner/karma/blob/master/CHANGELOG.md)
- [Commits](https://github.com/karma-runner/karma/compare/v6.3.14...v6.3.16)

---
updated-dependencies:
- dependency-name: karma
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>

They create installation problems on systems without an SSH key.

Ref: https://github.com/npm/cli/issues/2610#issuecomment-914610832

Bumps [karma](https://github.com/karma-runner/karma) from 5.1.1 to 6.3.14.
- [Release notes](https://github.com/karma-runner/karma/releases)
- [Changelog](https://github.com/karma-runner/karma/blob/master/CHANGELOG.md)
- [Commits](https://github.com/karma-runner/karma/compare/v5.1.1...v6.3.14)

---
updated-dependencies:
- dependency-name: karma
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>

* feat(multi-stream-support) Handle SDP munging for multiple local/remote streams/ep.
A new SDPSimulcast class is added for handling SDP munging for local and remote descriptions to handle multiple streams for both local and remote endpoints. This new class will be used only for unified plan implentation. The sdp-simucast npm package will be used for plan-b and deprecated later when all the clients switch to unified plan.

* fix(build) fix building with TS code

Use the Babel preset for the webpack bundle since Babel 7 already
understands TS and ts-loader uses tsc instead, which we configure
differently.

* squash: Add unit test and address review comments.

Co-authored-by: Saúl Ibarra Corretgé <saghul@jitsi.org>

Do it on the prepack step, so it gets built before we upload the build
artifact.

This is just the stepping stone towards the goal of eventually having
lib-jitsi-meet fully written in JS.

- introduce ts-loader for webpack
- webpack will continue generating the UMD bundle
- tsc will generate an ES6 module
- output all bundles to dist/