https://github.com/jitsi/lib-jitsi-meet/releases/tag/1343-2d21eb5b

This has 2 benefits:

a) it no longer needs to be built at install time, thus making builds faster

before:

real	0m46.865s
user	1m3.938s
sys	0m22.478s

after:

real	0m27.828s
user	0m25.582s
sys	0m21.699s

b) integrity errors go away since they are not computed over a locally
generated tarball

This is no longer supported as per the w3c spec for getDisplayMedia.

The CONFERENCE_WILL_LEAVE reducer in base/conference wipes the state so
we cannot rely on the old room value.

We may want to revisit this in the future.

This way we'll have proper tracebacks now.

This is the stepping stone for TypeScript support across Jitsi Meet. Currently
it makes it possible for lib-jitsi-meet to use TypeScript without adding any TS
code here yet.

In addition, replace the from with a div because they shouldn't be
nested.

Since we are no longer in a form, manually validate the password. This
was necessary regardless, because it was possible to bypass the digits
rule by pressing "add".

It triggers a security update alert, and use it through npx, so it
doesn't need to be in our package.json.

The Metro bundler gets confused and the result of such import statements
is `undefined`.

[0] introduced sorted language keys, but we had the assumption that the
first one meant to indicate the default language.

Break that assumption and be explicit about English being the default
language.

[0]: 7fe319d965

We don't recommend using the RN CLI due to the changes we make to the
standard RN project layout. Xcode and Android Studio should be used to
compile the app instead.

Keeping up with it has become untenable. With the last update (required
due to the RN bump) we have around 5k errors due to a major change in
how Flow operates: https://flow.org/en/docs/lang/types-first/

Fixing it is absolutely non-trivial, and at this point we better spend
that effort migrating to TypeScript instead.

If that alone wasn't a good enough reason, Facebook made it abundantly
clear they only care about Flow for themselves, not for the larger
community:
https://medium.com/flow-type/clarity-on-flows-direction-and-open-source-engagement-e721a4eb4d8b.
TypeScript has won the community.

"lookGood" represents a good condition.
However, "マイクが正常に動作していないようです" represents a bad
condition in Japanese.

In Japanese, "マイクは正常に動作しています" represents a good
condition.

* fix(RTC) skip DtlsTransport init if getSenders is missing
* feat(RTC) added DTLS transport monitoring
* fix(TPC) Do not change the tranceiver dir when the connection is not active. Fixes https://github.com/jitsi/jitsi-meet/issues/10754.

b088347043/...4baeb98964c6656b4ddb3fd5d355a9ddfa03fe74

* ref(JitsiConference) Add audio level handlers only for audio tracks. Other minor formatting changes.
* ref(TPC) Remove an unused method.
* ref(RTC) fix format and alpha sort the functions in JitsiLocalTrack.js.
* Fire settings error event
* feat(misc) add stalebot
* fix: use correct jsdoc types for params and methods

502aaf15b3/...b088347043f5de4dbffdfe02e750bdb55e595f30

This is the result of

    find lang -name "*.json" | while read file; do
      echo "Standardizing ${file}"
      t=$(mktemp)
      jq --indent 4 -S "." ${file} > ${t}
      mv ${t} ${file}
    done