AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Jitsi meet lib4/29/2023 Since we are using an NPM install, and not a local minified copy like JM does, we figure that script tag must be something like this: We have embedded the script tag as you’ve suggested but that does not enable the lib to be brought into React code and used. We are certainly very happy to share what works for us as we go forward if we can get some help integrating the package! Your help in getting to the bottom of what we are doing wrong will be very much appreciated, and I’m sure moving towards a working solution for TS React with the official LJM library will be very useful for the whole community. We have cloned the JM repo and looked around extensively to find how the lib is being implemented but still can’t figure out how to mirror what is working in JM. This is the heart of the matter for us, we can’t get it to work in this way, or trying to follow what we see in the JM repo. 'error', loadErrHandler, true /* capture phase type of listener */).'error', loadErrHandler, true /* capture phase */).If anyone who has steps to get around this, your help will be very much appreciated! We are still very much lost as to how this library can be imported and used in a React app! Now that the library is no longer being maintained, there are no actively maintained, typed modules to use LJM that we can find. Text: 'No matching export in "node_modules/lib-jitsi-meet/node_modules/strophe.js/dist/" for import "Strophe"' Try `npm i -save-dev if it exists or add a new declaration (.d.ts) file containing `declare module 'lib-jitsi-meet/dist/esm' `Īnd when creating a jitsi.d.ts file with declare module 'lib-jitsi-meet' the import errors go away but then the lib cannot be instantiated, giving a long list of Strophe errors similar to this when trying to serve the app: from 'strophe.js' ", '/Users/dgbau/src/jitsi-lib-test/node_modules/lib-jitsi-meet/dist/esm/index.js' implicitly has an 'any' type. When trying to import from lib-jitsi-meet/dist/esm this error is seen: Could not find a declaration file for module 'lib-jitsi-meet/dist/esm'. when installing lib-jitsi-meet via GitHub release as is done in Jitsi Meet, the package cannot be found when trying to import, with error: Cannot find module 'lib-jitsi-meet' or its corresponding type declarations. The more difficult problem I mentioned above is how to integrate the library overall though. How can I find out what version of lib-jitsi-meet is being used on our server install? The quick install version is bundled and there is no package.json file. "i18next-browser-languagedetector": "3.0.1",Īh, that’s very informative about the way versions are being used.This is how versions of lib-jitsi-meet are used in jitsi-meet jitsi/jitsi-meet/blob/d3d442e4d2230191f312ec12449c0aa9b9050e07/package.json#L82 On every build in ci the versions you see in code are replaced with the current jitsi-meet-web debian package version that is currently being built. The versions you see in index.html are only to be able to avoid caching. Now that we see the lib, and its predecessors, are no longer being maintained, we are wondering how to reliably build upon the lib-jitsi-meet package moving forward. My team and I have been developing prototype apps using the lib but we have run into some problems and wonder if are caused by version mis-matches between this lib and our server versions. Though the typing is a work in progress for is it still recommended to use these types in development? or should that app be treated as totally untyped? Are there and new guidelines for using this official repo in apps, React in particular, since the repo is no longer being maintained? how should these be correlated? and why is the version in the latest jitsi-meet master branch v=139? Is matching this version to the serverside package versions what is referred to? If so, how to correlate this version number with the versions in the lib-jitsi-meet repo? How does versioning work in lib-jitsi-meet? i see in my server that the version included in the index.html script tag is v=6854 but the highest version in the lib-jitsi-meet repo is 1557. It looks like repo was the best reccomended practice for typed installation via npm but now that the repo is read-only and not being maintained, what is? I’ll try and consolidate all of the questions/concerns here: I’ve run into some roadblocks lately using the lib-jitsi-meet library and have accumulated some questions about various angles of this.
0 Comments
Read More
Leave a Reply. |