@strevokit/meeting-sdk 0.0.0-stage → 0.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md ADDED
@@ -0,0 +1,96 @@
1
+ # Changelog
2
+
3
+ All notable changes to `@strevokit/meeting-sdk` are documented here. The format follows
4
+ [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the package follows
5
+ [semantic versioning](https://semver.org/). Before 1.0.0, breaking changes bump the minor version.
6
+
7
+ ## [Unreleased]
8
+
9
+ ## [0.8.0]
10
+
11
+ Bundles `@strevokit/signaling-protocol` 1.6.0.
12
+
13
+ ### Changed
14
+
15
+ - A live camera or microphone whose capture ends may continue on another device of that kind. The kind stays on, and
16
+ the change is not announced as stopped or started. When no other device of that kind can be opened, the kind turns
17
+ off and is announced as before.
18
+
19
+ ## [0.7.0]
20
+
21
+ Bundles `@strevokit/signaling-protocol` 1.6.0.
22
+
23
+ ### Added
24
+
25
+ - Connection state `reconnecting` for automatic meeting-service recovery after an unexpected drop while joined.
26
+ - Optional `getJoinToken` and `reconnectWindowMs` on `MeetingEngineOptions` so hosts can mint a fresh join token
27
+ during recovery (default recovery window 120 seconds).
28
+ - Media-path recovery while the room connection stays up: restart after a sustained interruption, and one bounded
29
+ link recreate after a failure within the recovery window.
30
+
31
+ ### Documentation
32
+
33
+ - Backend API guide covering `POST /v1/meetings`, `POST /v1/meetings/{public_id}/participants`,
34
+ `POST /v1/meetings/{public_id}/join-token`, and related embed-origin / get / end routes, with an Express-style
35
+ integration example.
36
+
37
+ ## [0.6.0]
38
+
39
+ Bundles `@strevokit/signaling-protocol` 1.6.0.
40
+
41
+ ### Changed
42
+
43
+ - Remote `screen` media is delivered in ordinary 1-to-1 peer meetings; shell consumers can render
44
+ `remoteMedia(id).screen`. When the meeting cannot carry screen bits, `startScreenShare()` rejects with
45
+ `unsupported_environment` before opening the display-capture prompt.
46
+
47
+ ## [0.5.0]
48
+
49
+ Bundles `@strevokit/signaling-protocol` 1.6.0.
50
+
51
+ ### Added
52
+
53
+ - `endMeeting()`: hosts can end the meeting for everyone. Sends `meeting.end` over signaling, resolving when the meeting is ended and every connection closes. Non-hosts reject with `not_permitted`; calls when not joined reject with `not_joined`.
54
+ - Close code 4004 mapped to `meeting_ended`.
55
+
56
+ ## [0.4.0]
57
+
58
+ Bundles `@strevokit/signaling-protocol` 1.5.0. No changes are needed in existing integrations.
59
+
60
+ ### Added
61
+
62
+ - Device choice: `enableCamera(options?)` and `unmute(options?)` accept `MediaDeviceOptions` with a `deviceId` from
63
+ `navigator.mediaDevices.enumerateDevices()`. Calling either while that device kind is already on switches to the
64
+ chosen device in place, without turning it off, so other participants see no interruption.
65
+ - A chosen device that is missing rejects with `device_not_found`, and a busy one with `device_unavailable`; the
66
+ device already in use keeps running.
67
+
68
+ ## [0.3.0]
69
+
70
+ Bundles `@strevokit/signaling-protocol` 1.5.0. Calls connect on more networks and stay connected through credential
71
+ renewals, with no changes needed in existing integrations.
72
+
73
+ ## [0.2.0]
74
+
75
+ Bundles `@strevokit/signaling-protocol` 1.4.0. No changes are needed in existing integrations.
76
+
77
+ ### Added
78
+
79
+ - Remote media: `remote_media_changed` event and `remoteMedia(participantId)`, so you can render other participants'
80
+ camera and microphone.
81
+ - Connection status per participant: `media_connection_changed` event and `mediaConnectionStatus(participantId)`.
82
+ - Error codes `media_connection_failed` and `media_participant_limit`.
83
+
84
+ ## [0.1.0]
85
+
86
+ Bundles `@strevokit/signaling-protocol` 1.3.0.
87
+
88
+ ### Added
89
+
90
+ - `createMeetingEngine(options)` returning a `MeetingEngine`: `join()`, `leave()`, `dispose()`, and the participant
91
+ list with each participant's role and media state.
92
+ - Local media controls: `enableCamera()`, `disableCamera()`, `mute()`, `unmute()`, `startScreenShare()`, and
93
+ `stopScreenShare()`, with `localMediaState` and `localMedia` for self-preview.
94
+ - Events: `state_changed`, `joined`, `participant_joined`, `participant_left`, `participant_reconnected`,
95
+ `participant_media_changed`, `local_media_changed`, `error`, and `closed`.
96
+ - `MeetingError` with stable codes, user-safe messages, and a `retryable` flag.
package/LICENSE ADDED
@@ -0,0 +1,215 @@
1
+ Copyright 2026 Agilia IT
2
+
3
+ Licensed under the Apache License, Version 2.0 (the "License");
4
+ you may not use this file except in compliance with the License.
5
+ You may obtain a copy of the License at
6
+
7
+ http://www.apache.org/licenses/LICENSE-2.0
8
+
9
+ Unless required by applicable law or agreed to in writing, software
10
+ distributed under the License is distributed on an "AS IS" BASIS,
11
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
12
+ See the License for the specific language governing permissions and
13
+ limitations under the License.
14
+
15
+ Apache License
16
+ Version 2.0, January 2004
17
+ http://www.apache.org/licenses/
18
+
19
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
20
+
21
+ 1. Definitions.
22
+
23
+ "License" shall mean the terms and conditions for use, reproduction,
24
+ and distribution as defined by Sections 1 through 9 of this document.
25
+
26
+ "Licensor" shall mean the copyright owner or entity authorized by
27
+ the copyright owner that is granting the License.
28
+
29
+ "Legal Entity" shall mean the union of the acting entity and all
30
+ other entities that control, are controlled by, or are under common
31
+ control with that entity. For the purposes of this definition,
32
+ "control" means (i) the power, direct or indirect, to cause the
33
+ direction or management of such entity, whether by contract or
34
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
35
+ outstanding shares, or (iii) beneficial ownership of such entity.
36
+
37
+ "You" (or "Your") shall mean an individual or Legal Entity
38
+ exercising permissions granted by this License.
39
+
40
+ "Source" form shall mean the preferred form for making modifications,
41
+ including but not limited to software source code, documentation
42
+ source, and configuration files.
43
+
44
+ "Object" form shall mean any form resulting from mechanical
45
+ transformation or translation of a Source form, including but
46
+ not limited to compiled object code, generated documentation,
47
+ and conversions to other media types.
48
+
49
+ "Work" shall mean the work of authorship, whether in Source or
50
+ Object form, made available under the License, as indicated by a
51
+ copyright notice that is included in or attached to the work
52
+ (an example is provided in the Appendix below).
53
+
54
+ "Derivative Works" shall mean any work, whether in Source or Object
55
+ form, that is based on (or derived from) the Work and for which the
56
+ editorial revisions, annotations, elaborations, or other modifications
57
+ represent, as a whole, an original work of authorship. For the purposes
58
+ of this License, Derivative Works shall not include works that remain
59
+ separable from, or merely link (or bind by name) to the interfaces of,
60
+ the Work and Derivative Works thereof.
61
+
62
+ "Contribution" shall mean any work of authorship, including
63
+ the original version of the Work and any modifications or additions
64
+ to that Work or Derivative Works thereof, that is intentionally
65
+ submitted to Licensor for inclusion in the Work by the copyright owner
66
+ or by an individual or Legal Entity authorized to submit on behalf of
67
+ the copyright owner. For the purposes of this definition, "submitted"
68
+ means any form of electronic, verbal, or written communication sent
69
+ to the Licensor or its representatives, including but not limited to
70
+ communication on electronic mailing lists, source code control systems,
71
+ and issue tracking systems that are managed by, or on behalf of, the
72
+ Licensor for the purpose of discussing and improving the Work, but
73
+ excluding communication that is conspicuously marked or otherwise
74
+ designated in writing by the copyright owner as "Not a Contribution."
75
+
76
+ "Contributor" shall mean Licensor and any individual or Legal Entity
77
+ on behalf of whom a Contribution has been received by Licensor and
78
+ subsequently incorporated within the Work.
79
+
80
+ 2. Grant of Copyright License. Subject to the terms and conditions of
81
+ this License, each Contributor hereby grants to You a perpetual,
82
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
83
+ copyright license to reproduce, prepare Derivative Works of,
84
+ publicly display, publicly perform, sublicense, and distribute the
85
+ Work and such Derivative Works in Source or Object form.
86
+
87
+ 3. Grant of Patent License. Subject to the terms and conditions of
88
+ this License, each Contributor hereby grants to You a perpetual,
89
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
90
+ (except as stated in this section) patent license to make, have made,
91
+ use, offer to sell, sell, import, and otherwise transfer the Work,
92
+ where such license applies only to those patent claims licensable
93
+ by such Contributor that are necessarily infringed by their
94
+ Contribution(s) alone or by combination of their Contribution(s)
95
+ with the Work to which such Contribution(s) was submitted. If You
96
+ institute patent litigation against any entity (including a
97
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
98
+ or a Contribution incorporated within the Work constitutes direct
99
+ or contributory patent infringement, then any patent licenses
100
+ granted to You under this License for that Work shall terminate
101
+ as of the date such litigation is filed.
102
+
103
+ 4. Redistribution. You may reproduce and distribute copies of the
104
+ Work or Derivative Works thereof in any medium, with or without
105
+ modifications, and in Source or Object form, provided that You
106
+ meet the following conditions:
107
+
108
+ (a) You must give any other recipients of the Work or
109
+ Derivative Works a copy of this License; and
110
+
111
+ (b) You must cause any modified files to carry prominent notices
112
+ stating that You changed the files; and
113
+
114
+ (c) You must retain, in the Source form of any Derivative Works
115
+ that You distribute, all copyright, patent, trademark, and
116
+ attribution notices from the Source form of the Work,
117
+ excluding those notices that do not pertain to any part of
118
+ the Derivative Works; and
119
+
120
+ (d) If the Work includes a "NOTICE" text file as part of its
121
+ distribution, then any Derivative Works that You distribute must
122
+ include a readable copy of the attribution notices contained
123
+ within such NOTICE file, excluding those notices that do not
124
+ pertain to any part of the Derivative Works, in at least one
125
+ of the following places: within a NOTICE text file distributed
126
+ as part of the Derivative Works; within the Source form or
127
+ documentation, if provided along with the Derivative Works; or,
128
+ within a display generated by the Derivative Works, if and
129
+ wherever such third-party notices normally appear. The contents
130
+ of the NOTICE file are for informational purposes only and
131
+ do not modify the License. You may add Your own attribution
132
+ notices within Derivative Works that You distribute, alongside
133
+ or as an addendum to the NOTICE text from the Work, provided
134
+ that such additional attribution notices cannot be construed
135
+ as modifying the License.
136
+
137
+ You may add Your own copyright statement to Your modifications and
138
+ may provide additional or different license terms and conditions
139
+ for use, reproduction, or distribution of Your modifications, or
140
+ for any such Derivative Works as a whole, provided Your use,
141
+ reproduction, and distribution of the Work otherwise complies with
142
+ the conditions stated in this License.
143
+
144
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
145
+ any Contribution intentionally submitted for inclusion in the Work
146
+ by You to the Licensor shall be under the terms and conditions of
147
+ this License, without any additional terms or conditions.
148
+ Notwithstanding the above, nothing herein shall supersede or modify
149
+ the terms of any separate license agreement you may have executed
150
+ with Licensor regarding such Contributions.
151
+
152
+ 6. Trademarks. This License does not grant permission to use the trade
153
+ names, trademarks, service marks, or product names of the Licensor,
154
+ except as required for reasonable and customary use in describing the
155
+ origin of the Work and reproducing the content of the NOTICE file.
156
+
157
+ 7. Disclaimer of Warranty. Unless required by applicable law or
158
+ agreed to in writing, Licensor provides the Work (and each
159
+ Contributor provides its Contributions) on an "AS IS" BASIS,
160
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
161
+ implied, including, without limitation, any warranties or conditions
162
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
163
+ PARTICULAR PURPOSE. You are solely responsible for determining the
164
+ appropriateness of using or redistributing the Work and assume any
165
+ risks associated with Your exercise of permissions under this License.
166
+
167
+ 8. Limitation of Liability. In no event and under no legal theory,
168
+ whether in tort (including negligence), contract, or otherwise,
169
+ unless required by applicable law (such as deliberate and grossly
170
+ negligent acts) or agreed to in writing, shall any Contributor be
171
+ liable to You for damages, including any direct, indirect, special,
172
+ incidental, or consequential damages of any character arising as a
173
+ result of this License or out of the use or inability to use the
174
+ Work (including but not limited to damages for loss of goodwill,
175
+ work stoppage, computer failure or malfunction, or any and all
176
+ other commercial damages or losses), even if such Contributor
177
+ has been advised of the possibility of such damages.
178
+
179
+ 9. Accepting Warranty or Additional Liability. While redistributing
180
+ the Work or Derivative Works thereof, You may choose to offer,
181
+ and charge a fee for, acceptance of support, warranty, indemnity,
182
+ or other liability obligations and/or rights consistent with this
183
+ License. However, in accepting such obligations, You may act only
184
+ on Your own behalf and on Your sole responsibility, not on behalf
185
+ of any other Contributor, and only if You agree to indemnify,
186
+ defend, and hold each Contributor harmless for any liability
187
+ incurred by, or claims asserted against, such Contributor by reason
188
+ of your accepting any such warranty or additional liability.
189
+
190
+ END OF TERMS AND CONDITIONS
191
+
192
+ APPENDIX: How to apply the Apache License to your work.
193
+
194
+ To apply the Apache License to your work, attach the following
195
+ boilerplate notice, with the fields enclosed by brackets "[]"
196
+ replaced with your own identifying information. (Don't include
197
+ the brackets!) The text should be enclosed in the appropriate
198
+ comment syntax for the file format. We also recommend that a
199
+ file or class name and description of purpose be included on the
200
+ same "printed page" as the copyright notice for easier
201
+ identification within third-party archives.
202
+
203
+ Copyright 2026 Agilia IT
204
+
205
+ Licensed under the Apache License, Version 2.0 (the "License");
206
+ you may not use this file except in compliance with the License.
207
+ You may obtain a copy of the License at
208
+
209
+ http://www.apache.org/licenses/LICENSE-2.0
210
+
211
+ Unless required by applicable law or agreed to in writing, software
212
+ distributed under the License is distributed on an "AS IS" BASIS,
213
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
214
+ See the License for the specific language governing permissions and
215
+ limitations under the License.
package/README.md CHANGED
@@ -1,3 +1,174 @@
1
- # Temporary Holding Version
1
+ # @strevokit/meeting-sdk
2
2
 
3
- This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
3
+ Embed Strevokit meetings in your web product.
4
+
5
+ The SDK is **headless**: it joins a meeting, keeps the participant list up to date, and controls the local camera,
6
+ microphone, and screen share. It has no UI and no runtime dependencies, so it works with any framework. Build your own
7
+ interface on top of it, or use the Strevokit UI components when they are available.
8
+
9
+ - Zero runtime dependencies, one ES module, full TypeScript types.
10
+ - One interface (`MeetingEngine`) for every meeting size. Your code never changes when the platform changes how media
11
+ is delivered.
12
+ - Stable error codes with user-safe messages.
13
+
14
+ ## Install
15
+
16
+ ```bash
17
+ npm install @strevokit/meeting-sdk
18
+ ```
19
+
20
+ The package is ESM-only and runs in browsers. Use it through a bundler (Vite, webpack, esbuild, and so on) or a native
21
+ `<script type="module">`.
22
+
23
+ ## Quick start
24
+
25
+ ### 1. Prepare the meeting on your backend
26
+
27
+ Your backend talks to the Strevokit HTTP API with its API credential, then returns only a short-lived join token to the
28
+ browser. **Never** send the API credential to the browser. Full request and response shapes:
29
+ [Backend API](./docs/backend-api.md).
30
+
31
+ ```ts
32
+ // Server side. Headers on every call:
33
+ // Authorization: Bearer ${process.env.STREVOKIT_API_CREDENTIAL}
34
+ // Content-Type: application/json
35
+ const api = "https://api.example.com"; // your Strevokit API base URL
36
+ const headers = {
37
+ Authorization: `Bearer ${process.env.STREVOKIT_API_CREDENTIAL}`,
38
+ "Content-Type": "application/json",
39
+ };
40
+
41
+ // Once per environment: allow-list the origin that hosts your page.
42
+ await fetch(`${api}/v1/embed-origins`, {
43
+ method: "POST",
44
+ headers,
45
+ body: JSON.stringify({ origin: "https://app.example.com" }),
46
+ });
47
+
48
+ // Create the meeting, then authorize each person who may join.
49
+ const { data: meeting } = await fetch(`${api}/v1/meetings`, {
50
+ method: "POST",
51
+ headers,
52
+ body: JSON.stringify({ type: "one_to_one", max_participants: 2 }),
53
+ }).then((r) => r.json());
54
+
55
+ const { data: participant } = await fetch(`${api}/v1/meetings/${meeting.public_id}/participants`, {
56
+ method: "POST",
57
+ headers,
58
+ body: JSON.stringify({
59
+ external_user_id: "user_42",
60
+ display_name: "Alex",
61
+ role: "host",
62
+ }),
63
+ }).then((r) => r.json());
64
+
65
+ // When the signed-in user opens the meeting page, mint a join token and return only data.token.
66
+ const { data } = await fetch(`${api}/v1/meetings/${meeting.public_id}/join-token`, {
67
+ method: "POST",
68
+ headers,
69
+ body: JSON.stringify({ participant_public_id: participant.public_id }),
70
+ }).then((r) => r.json()); // { token, expires_at, expires_in }
71
+ ```
72
+
73
+ ### 2. Join from the browser
74
+
75
+ ```ts
76
+ import { createMeetingEngine, MeetingError } from "@strevokit/meeting-sdk";
77
+
78
+ const engine = createMeetingEngine({
79
+ token, // from your backend
80
+ realtimeUrl: "wss://realtime.example.com", // your Strevokit realtime endpoint
81
+ });
82
+
83
+ engine.on("joined", ({ self, participants }) => {
84
+ console.log(`Joined as ${self.role} with ${participants.length} others`);
85
+ });
86
+ engine.on("participant_joined", ({ participant }) => addTile(participant));
87
+ engine.on("participant_left", ({ participantId }) => removeTile(participantId));
88
+ engine.on("participant_media_changed", ({ participantId, kind, enabled }) => updateTile(participantId, kind, enabled));
89
+ engine.on("closed", ({ reason, error }) => showEndScreen(reason, error?.message));
90
+
91
+ try {
92
+ await engine.join();
93
+ } catch (error) {
94
+ if (error instanceof MeetingError) showError(error.message); // safe to show to users
95
+ }
96
+ ```
97
+
98
+ ### 3. Control media
99
+
100
+ ```ts
101
+ await engine.enableCamera();
102
+ selfPreview.srcObject = engine.localMedia.camera; // a MediaStream for a <video> element
103
+
104
+ await engine.unmute();
105
+ await engine.startScreenShare(); // rejects with `not_permitted` if your role may not share
106
+ ```
107
+
108
+ Every media method is idempotent and rejects with a `MeetingError` (for example `permission_denied` or
109
+ `device_not_found`) without changing any state.
110
+
111
+ ### 4. Show other participants
112
+
113
+ ```ts
114
+ engine.on("remote_media_changed", ({ participantId, kind, stream }) => {
115
+ if (kind === "camera") videoFor(participantId).srcObject = stream; // a <video autoplay playsinline muted>
116
+ if (kind === "microphone") audioFor(participantId).srcObject = stream; // an <audio autoplay>
117
+ });
118
+ engine.on("media_connection_changed", ({ participantId, status }) => {
119
+ // "connecting" | "connected" | "interrupted" | "failed", or null when there is no connection any more
120
+ showStatus(participantId, status);
121
+ });
122
+ ```
123
+
124
+ `stream` is `null` when that media stops being available. `engine.remoteMedia(participantId)` and
125
+ `engine.mediaConnectionStatus(participantId)` return the current values at any time.
126
+
127
+ ### 5. Leave
128
+
129
+ ```ts
130
+ await engine.leave(); // releases camera, microphone, and screen; then `closed` fires with reason "left"
131
+ ```
132
+
133
+ An engine joins once. To join again, mint a new token and create a new engine. Call `engine.dispose()` when your
134
+ component unmounts; it releases everything immediately and emits nothing.
135
+
136
+ More examples: [plain HTML](./docs/examples/vanilla.html), [React](./docs/examples/react.tsx), and
137
+ [backend integration](./docs/examples/backend-integration.md).
138
+
139
+ ## Browser support
140
+
141
+ Current versions of Chrome, Edge, Firefox, and Safari. The page must be served over HTTPS (browsers only allow camera,
142
+ microphone, and screen access in secure contexts). In an unsupported browser the SDK throws or rejects with
143
+ `unsupported_environment`.
144
+
145
+ ## Security
146
+
147
+ - **The join token stays in memory.** The SDK sends it only during the connection handshake. It never appears in URLs,
148
+ storage, events, error messages, or log output.
149
+ - **Identity comes from the token.** Role and participant identity are decided by your backend when it mints the token.
150
+ The SDK never sends a role or identity of its own.
151
+ - **Embed origins are allow-listed.** Joins are accepted only from the origins configured for your tenant. A join from
152
+ any other site fails with `origin_not_allowed`.
153
+ - **Local development.** `realtimeUrl` must use `wss://`. Plain `ws://` is accepted only for `localhost` and
154
+ `127.0.0.1`.
155
+
156
+ ## Versioning
157
+
158
+ The package follows [semantic versioning](https://semver.org/). The public API is exactly what
159
+ [docs/api-reference.md](./docs/api-reference.md) describes. Before 1.0.0, breaking changes bump the minor version; from
160
+ 1.0.0 they bump the major version. New event types and error codes may be added in minor versions, so handle unknown
161
+ values generically. See the [changelog](./CHANGELOG.md).
162
+
163
+ ## Documentation
164
+
165
+ - [Backend API](./docs/backend-api.md): create meeting, authorize participants, mint join tokens, and related routes
166
+ (`POST` / `GET` / `DELETE` with request and response shapes).
167
+ - [API reference](./docs/api-reference.md): every export, method, event, error code, and close reason.
168
+ - [Examples](./docs/examples/).
169
+
170
+ ## Source and releases
171
+
172
+ The source is published at [github.com/AgiliaIT/strevokit-meeting-sdk](https://github.com/AgiliaIT/strevokit-meeting-sdk).
173
+ Releases are published to npm from that repository with npm provenance, and tagged `meeting-sdk-v<version>`. Report
174
+ problems through its [issues](https://github.com/AgiliaIT/strevokit-meeting-sdk/issues).