fix(node-sdk): include userId when syncing company context #2773
roncohenAnnotations
10 errors and 1 warning
|
Build & Test
Property 'flagsPushUrl' does not exist on type 'ClientOptions'.
|
|
Build & Test
Property 'flagsPushUrl' does not exist on type 'ClientOptions'.
|
|
Build & Test
Property 'flagsPushUrl' does not exist on type 'ClientOptions'.
|
|
Build & Test
Property 'flagsSyncMode' does not exist on type 'ClientOptions'.
|
|
Build & Test
Property 'flagsSyncMode' does not exist on type 'ClientOptions'.
|
|
Build & Test
Property 'flagsSyncMode' does not exist on type 'ClientOptions'.
|
|
Build & Test
Property 'flagsSyncMode' does not exist on type 'ClientOptions'.
|
|
Build & Test
Module '"./types"' has no exported member 'FlagsSyncMode'.
|
|
Build & Test
Cannot find module './flag-updates-sse' or its corresponding type declarations.
|
|
Build & Test
Module '"./config"' has no exported member 'PUBSUB_SSE_URL'.
|
|
Build & Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|