When using any optimizely function on ssr uuid dependency breaks

[lorenzo-lungo]

Is there an existing issue for this?

• I have searched the existing issues

SDK Version

6.0.0

Current Behavior

When importing uuid on server side (no matter where) this is the log I get

Cannot read properties of undefined (reading 'v1')

Cannot read properties of undefined (reading 'v1') at /Users/lorenzolungo/Work/canvas-storefront/node_modules/.pnpm/uuid@10.0.0/node_modules/uuid/wrapper.mjs:16:42) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async ViteNodeRunner.runModule (/Users/lorenzolungo/Work/canvas-storefront/node_modules/.pnpm/vite-node@3.2.4_@types+node@24.0.14_jiti@2.4.2_terser@5.43.1_yaml@2.8.0/node_modules/vite-node/dist/client.mjs:397:4) at async ViteNodeRunner.directRequest (/Users/lorenzolungo/Work/canvas-storefront/node_modules/.pnpm/vite-node@3.2.4_@types+node@24.0.14_jiti@2.4.2_terser@5.43.1_yaml@2.8.0/node_modules/vite-node/dist/client.mjs:375:3) at async ViteNodeRunner.cachedRequest (/Users/lorenzolungo/Work/canvas-storefront/node_modules/.pnpm/vite-node@3.2.4_@types+node@24.0.14_jiti@2.4.2_terser@5.43.1_yaml@2.8.0/node_modules/vite-node/dist/client.mjs:189:11) at async ViteNodeRunner.dependencyRequest (/Users/lorenzolungo/Work/canvas-storefront/node_modules/.pnpm/vite-node@3.2.4_@types+node@24.0.14_jiti@2.4.2_terser@5.43.1_yaml@2.8.0/node_modules/vite-node/dist/client.mjs:239:10) at async /Users/lorenzolungo/Work/canvas-storefront/node_modules/.pnpm/@optimizely+optimizely-sdk@6.0.0_ua-parser-js@1.0.40/node_modules/@optimizely/optimizely-sdk/dist/index.node.es.min.mjs:22:31) at async ViteNodeRunner.runModule (/Users/lorenzolungo/Work/canvas-storefront/node_modules/.pnpm/vite-node@3.2.4_@types+node@24.0.14_jiti@2.4.2_terser@5.43.1_yaml@2.8.0/node_modules/vite-node/dist/client.mjs:397:4) at async ViteNodeRunner.directRequest (/Users/lorenzolungo/Work/canvas-storefront/node_modules/.pnpm/vite-node@3.2.4_@types+node@24.0.14_jiti@2.4.2_terser@5.43.1_yaml@2.8.0/node_modules/vite-node/dist/client.mjs:375:3) at async ViteNodeRunner.cachedRequest (/Users/lorenzolungo/Work/canvas-storefront/node_modules/.pnpm/vite-node@3.2.4_@types+node@24.0.14_jiti@2.4.2_terser@5.43.1_yaml@2.8.0/node_modules/vite-node/dist/client.mjs:189:11)

Expected Behavior

It should correctly import the dependency

I was able to avoid the issue by downgrading uuid dependency to version 7.0.3 by doing

"overrides": {
      "@optimizely/optimizely-sdk>uuid": "7.0.3"
    },

Steps To Reproduce

In a nuxt (or next environment), or in a node server side environment
Import the @optimizely/optimizely-sdk anywhere and be sure that that part of the code runs server side
Notice that the issue reported above happens

SDK Type

Node

Node Version

22.15.0

Browsers impacted

The issue is server side

Link

No response

Logs

Cannot read properties of undefined (reading 'v1')

Cannot read properties of undefined (reading 'v1') at /Users/lorenzolungo/Work/canvas-storefront/node_modules/.pnpm/uuid@10.0.0/node_modules/uuid/wrapper.mjs:16:42) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async ViteNodeRunner.runModule (/Users/lorenzolungo/Work/canvas-storefront/node_modules/.pnpm/vite-node@3.2.4_@types+node@24.0.14_jiti@2.4.2_terser@5.43.1_yaml@2.8.0/node_modules/vite-node/dist/client.mjs:397:4) at async ViteNodeRunner.directRequest (/Users/lorenzolungo/Work/canvas-storefront/node_modules/.pnpm/vite-node@3.2.4_@types+node@24.0.14_jiti@2.4.2_terser@5.43.1_yaml@2.8.0/node_modules/vite-node/dist/client.mjs:375:3) at async ViteNodeRunner.cachedRequest (/Users/lorenzolungo/Work/canvas-storefront/node_modules/.pnpm/vite-node@3.2.4_@types+node@24.0.14_jiti@2.4.2_terser@5.43.1_yaml@2.8.0/node_modules/vite-node/dist/client.mjs:189:11) at async ViteNodeRunner.dependencyRequest (/Users/lorenzolungo/Work/canvas-storefront/node_modules/.pnpm/vite-node@3.2.4_@types+node@24.0.14_jiti@2.4.2_terser@5.43.1_yaml@2.8.0/node_modules/vite-node/dist/client.mjs:239:10) at async /Users/lorenzolungo/Work/canvas-storefront/node_modules/.pnpm/@optimizely+optimizely-sdk@6.0.0_ua-parser-js@1.0.40/node_modules/@optimizely/optimizely-sdk/dist/index.node.es.min.mjs:22:31) at async ViteNodeRunner.runModule (/Users/lorenzolungo/Work/canvas-storefront/node_modules/.pnpm/vite-node@3.2.4_@types+node@24.0.14_jiti@2.4.2_terser@5.43.1_yaml@2.8.0/node_modules/vite-node/dist/client.mjs:397:4) at async ViteNodeRunner.directRequest (/Users/lorenzolungo/Work/canvas-storefront/node_modules/.pnpm/vite-node@3.2.4_@types+node@24.0.14_jiti@2.4.2_terser@5.43.1_yaml@2.8.0/node_modules/vite-node/dist/client.mjs:375:3) at async ViteNodeRunner.cachedRequest (/Users/lorenzolungo/Work/canvas-storefront/node_modules/.pnpm/vite-node@3.2.4_@types+node@24.0.14_jiti@2.4.2_terser@5.43.1_yaml@2.8.0/node_modules/vite-node/dist/client.mjs:189:11)

Severity

Blocking development

Workaround/Solution

No response

Recent Change

Yes, after the 6.0.0 update

Conflicts

No response

[raju-opti]

Hey @lorenzo-lungo , thanks for reporting the issue. Let me try to reproduce it and get back to you.

[raju-opti]

Hello @lorenzo-lungo , I tried to reproduce this using a basic NodeJS project and also using NextJS server component. In both cases, the decide() method is working fine. Please note that, decide dispatches an impression event and we use the uuid module to generate ids for the events. This is the repository: https://github.com/raju-opti/issue_1078. Any additional info that helps to reproduce this is greatly appreciated.

[lorenzo-lungo]

What I don't get about your example (but maybe it is because I am way more familiar with nuxt than with next) is that I do not see any place where you are importing the sdk that is server side only, I think the issue happens when a file imports ths sdk and that file is run server side (in our case in a server plugin in nuxt but I suppose a lot of other similar places will make the trick), notice that we figured out that the 11.0.0 version of uuid package works fine so if you can just update that without breaking other stuff it will do the trick without a lot of further investigation from your side

[raju-opti]

@lorenzo-lungo there is also a plain NodeJS project as well in the repo, which works correctly as well (https://github.com/raju-opti/issue_1078/tree/main/vanilla-node). For the next project, the import is here: https://github.com/raju-opti/issue_1078/blob/main/nextjs/src/lib/optimizely.ts (This is used in a server component here: https://github.com/raju-opti/issue_1078/blob/main/nextjs/src/app/page.tsx). It would be great if you could make a PR to the repo with a minimal example that reproduces the issue, or give some pointers about how to reproduce it. In the meantime, I will try with a Nuxt project.

Unfortunately we cannot readily update to uuid@11 at that moment cause our build breaks for uuid@11.

[raju-opti]

@lorenzo-lungo another thing, we don't import v1 uuid anywhere in our sdk (we only use v4 uuids). So I am wondering where the error message Cannot read properties of undefined (reading 'v1') coming from.

[raju-opti]

Hello @lorenzo-lungo , I tried to reproduce using a Nuxt app, executing decide() in a nitro plugin. (I am not familiar with Nuxt, took help from AI set it up). Everything seem to work fine here as well. Here is the demo app: https://github.com/raju-opti/issue_1078/tree/main/nuxtjs. Could you please review and give some suggestions how to reproduce?