# mediasoup-client 3.9.3: Incorrect version constant

**URL:** <https://mediasoup.discourse.group/t/mediasoup-client-3-9-3-incorrect-version-constant/6574>\
**Category:** mediasoup libraries\
**Created:** [March 21, 2025, 1:25pm UTC](https://mediasoup.discourse.group/t/mediasoup-client-3-9-3-incorrect-version-constant/6574 "2025-03-21T13:25:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![miroslavpejic85](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/miroslavpejic85/32/1044_2.png) [@miroslavpejic85](https://mediasoup.discourse.group/u/miroslavpejic85)\
**Post date:** [March 21, 2025, 1:25pm UTC](https://mediasoup.discourse.group/t/mediasoup-client-3-9-3-incorrect-version-constant/6574/1 "2025-03-21T13:25:08Z")

</div>

In version 3.9.3, the `version` constant is defined as:

```js
export declare const version = " __MEDIASOUP_CLIENT_VERSION__";

```

instead of the expected version string. This appears to be a build or packaging issue where the placeholder was not properly replaced during the release process.

In the previous version (3.9.2), the value was correctly set:

```js
/**
 * Expose mediasoup-client version.
 */
export declare const version = "3.9.2";

```

Thank you!

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [March 21, 2025, 3:34pm UTC](https://mediasoup.discourse.group/t/mediasoup-client-3-9-3-incorrect-version-constant/6574/2 "2025-03-21T15:34:40Z")

</div>

> [@miroslavpejic85](#):
>
> In version 3.9.3, the `version` constant is defined as:
> 
> ```auto
> export declare const version = " __MEDIASOUP_CLIENT_VERSION__";
> 
> ```

This is not true.

mediasoup-client-aiortc uses mediasoup-client 3.9.1 rather than 3.9.3 and that’s a fixed version as per `package-lock.json` in mediasoup-client-aiortc:

```json
		"node_modules/mediasoup-client": {
			"version": "3.9.1",
			"resolved": "https://registry.npmjs.org/mediasoup-client/-/mediasoup-client-3.9.1.tgz",

```

In mediasoup-client 3.9.3, the generated `lib/` folder (which is the one present in the NPM package and contains transpiled `.js` files and TypeScript declarations in `.d.ts` files) the `version` constant is ok. You cna verify that within `mediasoup-client/lib` folder there is NO `MEDIASOUP_CLIENT_VERSION` string at all.

So the problem is probably that you are somehow using mediasoup-client-aiortc with the latest version of mediasoup-client which is not supported without pending changes in mediasoup-client-aiortc, but again: latest mediasoup-client-aiortc doesn’t depend on mediasoup-client 3.9.3 but on 3.9.1, so this is something in your local setup in which you are updating mediasoup-client version in latest mediasoup-client-aiortc code, but that’s not how it is supposed to be,.

---

<div class="post-metadata">

**Author:** ![miroslavpejic85](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/miroslavpejic85/32/1044_2.png) [@miroslavpejic85](https://mediasoup.discourse.group/u/miroslavpejic85)\
**Post date:** [March 21, 2025, 9:18pm UTC](https://mediasoup.discourse.group/t/mediasoup-client-3-9-3-incorrect-version-constant/6574/3 "2025-03-21T21:18:50Z")

</div>

> [@ibc](#):
>
> You cna verify that within `mediasoup-client/lib` folder there is NO `MEDIASOUP_CLIENT_VERSION` string at all.

I’m verify as you said, and also trying with the latest **mediasoup-client 3.9.4** :

> **[mediasoup-client](https://www.npmjs.com/package/mediasoup-client)**
>
> mediasoup client side TypeScript library. Latest version: 3.9.4, last published: 5 hours ago. Start using mediasoup-client in your project by running \`npm i mediasoup-client\`. There are 124 other projects in the npm registry using mediasoup-client.

**package.json**

```js
"mediasoup-client": "3.9.4",

```

**package.look.json**

```js
        "node_modules/mediasoup-client": {
            "version": "3.9.4",
            "resolved": "https://registry.npmjs.org/mediasoup-client/-/mediasoup-client-3.9.4.tgz",

```

  

I took a closer look, and I believe there might be a misunderstanding. The ` __MEDIASOUP_CLIENT_VERSION__ ` string **does** exist in `mediasoup-client/lib`, specifically in `lib/index.js` and `lib/index.d.ts`.

After checking version **3.9.4** , running:

```sh
grep " __MEDIASOUP_CLIENT_VERSION__" -r node_modules/mediasoup-client

```

I found:

- `lib/index.js`:

```js
exports.version = ' __MEDIASOUP_CLIENT_VERSION__';

```

- `lib/index.d.ts`:

```js
export declare const version = " __MEDIASOUP_CLIENT_VERSION__";

```

- `npm-scripts.mjs`:

```js
const result = text.replace(/ __MEDIASOUP_CLIENT_VERSION__ /g, PKG.version);

```

Additionally, when I run:

```js
const mediasoupClient = require('mediasoup-client');
console.log(mediasoupClient.version);

```

The result is:

- **3.9.4** → `' __MEDIASOUP_CLIENT_VERSION__'`
- **3.9.2** → `'3.9.2'`

It looks like in **3.9.4** , the build process is not replacing ` __MEDIASOUP_CLIENT_VERSION__ ` correctly, which might be causing confusion.

Hope this helps clarify things! Thank you 😊

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [March 21, 2025, 9:32pm UTC](https://mediasoup.discourse.group/t/mediasoup-client-3-9-3-incorrect-version-constant/6574/4 "2025-03-21T21:32:47Z")

</div>

You are right. It’0s fixed in 3.9.5: [3.9.5 · versatica/mediasoup-client@0e6f651 · GitHub](https://github.com/versatica/mediasoup-client/commit/0e6f65170d902d3221ef7f5e269a5d3155acde72)

Thanks a lot.