[Team Name] Can't import `nagaDev` in v8

[CodeSandwich]

Is there an existing issue for this?

• I have searched the existing issues

SDK version

8.0.2

Lit Network

Wished

Description of the bug/issue

Importing @lit-protocol/networks causes an error.

Severity of the bug

Negative severity. It prevents the usage of Lit and exposure to any risks. Couldn't be safer.

Steps To Reproduce

I have a trivial node.js project with this package.json:

{
  "name": "oracle",
  "version": "0.0.1",
  "scripts": {
    "sandbox": "node -e 'require(`./index.js`).sandbox()'"
  },
  "dependencies": {
    "@lit-protocol/lit-client": "^8.0.2",
    "@lit-protocol/networks": "^8.0.2"
  }
}

and this index.js:

import { nagaDev } from "@lit-protocol/networks";
export async function sandbox() {}

After removing node_modules and package_lock.json and running npm install, I tried running npm run sandbox and got this error:

> oracle@0.0.1 sandbox
> node -e 'require(`./oracle.js`).sandbox()'

lit-js-sdk:constants:errors deprecated LitErrorKind is deprecated and will be removed in a future version. Use LIT_ERROR_KIND instead. node:internal/modules/cjs/loader:1734:14
file:///home/zuczek/workspace/drips-contracts/oracle/node_modules/@wagmi/core/dist/esm/actions/sendCallsSync.js:1
import { sendCallsSync as viem_sendCallsSync, } from 'viem/actions';
         ^^^^^^^^^^^^^

SyntaxError: The requested module 'viem/actions' does not provide an export named 'sendCallsSync'
    at ModuleJobSync.runSync (node:internal/modules/esm/module_job:387:37)
    at ModuleLoader.importSyncForRequire (node:internal/modules/esm/loader:427:47)
    at loadESMFromCJS (node:internal/modules/cjs/loader:1565:24)
    at Module._compile (node:internal/modules/cjs/loader:1716:5)
    at Object..js (node:internal/modules/cjs/loader:1899:10)
    at Module.load (node:internal/modules/cjs/loader:1469:32)
    at Function._load (node:internal/modules/cjs/loader:1286:12)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:235:24)
    at Module.require (node:internal/modules/cjs/loader:1491:12)

Node.js v23.11.0

Link to code

No response

Anything else?

No response

[CodeSandwich]

I fixed it by installing "@lit-protocol/auth-services": "^2.0.2". It seems that @lit-protocol/networks implicitly requires a dependency of @lit-protocol/auth-services. I'll keep this issue open because it's still a bug and because it derails the tutorial by requiring in the first sub-chapter dependencies that won't be installed for 3 more sub-chapters.

[Ansonhkg]

hi @CodeSandwich I've noticed this issue too and raised a PR here:
#957

You could also try the snapshot releases there to confirm if the PR fixes this for you

[Ansonhkg]

@CodeSandwich If the snapshots work for you, could you please let me know?

[CodeSandwich]

Thanks @Ansonhkg, what a coincidence 😆 I'd love to try it out, but I can't set the dependency, NPM must be the crappiest package manager I've ever used. There's no way to specify a git repository subdirectory as the package location and there's no way to pick the package from the dependency's workspace. NPM has multiple issues open on the topic, most of them closed by the maintainers. I tried using GitPkg, but NPM throws arcane errors during installation. Is the only way forward to clone the repo and add it as a local filesystem dependency? That would be good enough for a one-off test, but not an actual dependency.

Edit: I actually can't seem to install from a local clone either, having the dependency "@lit-protocol/networks": "../lit-protocol-js-sdk/packages/networks" causes ERR_MODULE_NOT_FOUND due to Error: Cannot find package '/home/zuczek/workspace/drips-contracts/oracle/node_modules/@lit-protocol/networks/index.js' imported from /home/zuczek/workspace/drips-contracts/oracle/index.js. It makes sense since there's no @lit-protocol/networks/index.js, there's only .ts, so I probably should manually compile TS to JS first?

[Ansonhkg]

@CodeSandwich I was referring to the snapshot versions in the description, I'll copy & paste here:

#957

🦋  New tag:  @lit-protocol/auth@0.0.0-20251016165432
🦋  New tag:  @lit-protocol/auth-helpers@0.0.0-20251016165432
🦋  New tag:  @lit-protocol/auth-services@0.0.0-20251016165432
🦋  New tag:  @lit-protocol/constants@0.0.0-20251016165432
🦋  New tag:  @lit-protocol/contracts@0.0.0-20251016165432
🦋  New tag:  @lit-protocol/e2e@0.0.0-20251016165432
🦋  New tag:  @lit-protocol/lit-client@0.0.0-20251016165432
🦋  New tag:  @lit-protocol/networks@0.0.0-20251016165432

As for local clone, yea, you will need to use pnpm to install pnpm install and build pnpm build, but you shouldn't need to do that, you can simply try the versions above.

[CodeSandwich]

Thanks, I haven't noticed it! It's a nice workaround for testing, but I still can't confirm whether it's fixed or not. I have this in package.json:

  "dependencies": {
    "@lit-protocol/lit-client": "=0.0.0-20251016165432",
    "@lit-protocol/networks": "=0.0.0-20251016165432"
  }

I keep getting the error. I tried removing both package-lock.json and node_modules to make it fully clean, but package-lock.json still describes @lit-protocol/networks as:

    "node_modules/@lit-protocol/networks": {
      "version": "0.0.0-20251016165432",
      "resolved": "https://registry.npmjs.org/@lit-protocol/networks/-/networks-0.0.0-20251016165432.tgz",
      "integrity": "sha512-sHBVztvtqrvSoKHv8es+5EDDigrca7y+xVcGHvnTigZ6UBMyTxpOvjLhMczFtPIVqvk+qPivE71tryJf5aDYHg==",
      "license": "MIT",
      "dependencies": {
        "@ethersproject/contracts": "5.8.0",
        "@ethersproject/providers": "5.7.0",
        "@ethersproject/transactions": "5.7.0",
        "@jest/globals": "29.7.0",
        "@lit-protocol/access-control-conditions": "8.0.2",
        "@lit-protocol/access-control-conditions-schemas": "8.0.2",
        "@lit-protocol/auth-helpers": "0.0.0-20251016165432",
        "@lit-protocol/constants": "0.0.0-20251016165432",
        "@lit-protocol/contracts": "0.0.0-20251016165432",
        "@lit-protocol/crypto": "8.0.2",
        "@lit-protocol/logger": "8.0.2",
        "@lit-protocol/nacl": "7.1.1",
        "@lit-protocol/schemas": "8.0.2",
        "@lit-protocol/types": "8.0.2",
        "@lit-protocol/uint8arrays": "7.1.1",
        "@lit-protocol/wasm": "8.0.2",
        "@noble/curves": "^1.8.1",
        "@noble/hashes": "^1.8.0",
        "@openagenda/verror": "^3.1.4",
        "@t3-oss/env-core": "0.13.8",
        "@typechain/ethers-v6": "0.5.1",
        "@wagmi/core": "^2.17.1",
        "ajv": "^8.12.0",
        "bs58": "^6.0.0",
        "ethers": "^5.7.1",
        "node-localstorage": "^3.0.5",
        "pako": "^2.1.0",
        "pino": "^9.6.0",
        "pino-caller": "^4.0.0",
        "siwe": "^2.3.2",
        "siwe-recap": "0.0.2-alpha.0",
        "tslib": "^2.8.1",
        "typechain": "8.3.2",
        "zod": "3.24.3",
        "zod-validation-error": "3.4.0"
      },
      "peerDependencies": {
        "viem": "2.29.4"
      }
    },

As you can see, there's a mixture of test builds and regular releases of @lit-protocol packages. It's not clear to me what path the bug goes and whether it would be fixed if all packages are patched.

[Ansonhkg]

Thanks, I haven't noticed it! It's a nice workaround for testing, but I still can't confirm whether it's fixed or not. I have this in package.json:

"dependencies": {
"@lit-protocol/lit-client": "=0.0.0-20251016165432",
"@lit-protocol/networks": "=0.0.0-20251016165432"
}
I keep getting the error. I tried removing both package-lock.json and node_modules to make it fully clean, but package-lock.json still describes @lit-protocol/networks as:

"node_modules/@lit-protocol/networks": {
  "version": "0.0.0-20251016165432",
  "resolved": "https://registry.npmjs.org/@lit-protocol/networks/-/networks-0.0.0-20251016165432.tgz",
  "integrity": "sha512-sHBVztvtqrvSoKHv8es+5EDDigrca7y+xVcGHvnTigZ6UBMyTxpOvjLhMczFtPIVqvk+qPivE71tryJf5aDYHg==",
  "license": "MIT",
  "dependencies": {
    "@ethersproject/contracts": "5.8.0",
    "@ethersproject/providers": "5.7.0",
    "@ethersproject/transactions": "5.7.0",
    "@jest/globals": "29.7.0",
    "@lit-protocol/access-control-conditions": "8.0.2",
    "@lit-protocol/access-control-conditions-schemas": "8.0.2",
    "@lit-protocol/auth-helpers": "0.0.0-20251016165432",
    "@lit-protocol/constants": "0.0.0-20251016165432",
    "@lit-protocol/contracts": "0.0.0-20251016165432",
    "@lit-protocol/crypto": "8.0.2",
    "@lit-protocol/logger": "8.0.2",
    "@lit-protocol/nacl": "7.1.1",
    "@lit-protocol/schemas": "8.0.2",
    "@lit-protocol/types": "8.0.2",
    "@lit-protocol/uint8arrays": "7.1.1",
    "@lit-protocol/wasm": "8.0.2",
    "@noble/curves": "^1.8.1",
    "@noble/hashes": "^1.8.0",
    "@openagenda/verror": "^3.1.4",
    "@t3-oss/env-core": "0.13.8",
    "@typechain/ethers-v6": "0.5.1",
    "@wagmi/core": "^2.17.1",
    "ajv": "^8.12.0",
    "bs58": "^6.0.0",
    "ethers": "^5.7.1",
    "node-localstorage": "^3.0.5",
    "pako": "^2.1.0",
    "pino": "^9.6.0",
    "pino-caller": "^4.0.0",
    "siwe": "^2.3.2",
    "siwe-recap": "0.0.2-alpha.0",
    "tslib": "^2.8.1",
    "typechain": "8.3.2",
    "zod": "3.24.3",
    "zod-validation-error": "3.4.0"
  },
  "peerDependencies": {
    "viem": "2.29.4"
  }
},

As you can see, there's a mixture of test builds and regular releases of @lit-protocol packages. It's not clear to me what path the bug goes and whether it would be fixed if all packages are patched.

It looks like you have correctly installed the packages, but you're saying you are getting the same error? If possible, could paste your error here, and could you also create a reproducible repo so I can test it?

re: a mixture of test builds and regular releases..

Yeah, that’s by design. If a dependency hasn’t actually changed, we don’t bump its version. Only the affected packages are versioned together. In this case, auth-helpers, constants, and contracts are the ones that were updated. In v7 though, all packages are versioned together.

[CodeSandwich]

It looks like you have correctly installed the packages, but you're saying you are getting the same error? If possible, could paste your error here, and could you also create a reproducible repo so I can test it?

Yes, it's the same error. It's in the original message along with the entire code of the failing project, there's not much to clone really, you can copy-paste those 2 files. If it matters, I have NPM 11.4.2 and NodeJS v23.11.0. Please let me know if you can reproduce the issue.

[Ansonhkg]

It looks like you have correctly installed the packages, but you're saying you are getting the same error? If possible, could paste your error here, and could you also create a reproducible repo so I can test it?

Yes, it's the same error. It's in the original message along with the entire code of the failing project, there's not much to clone really, you can copy-paste those 2 files. If it matters, I have NPM 11.4.2 and NodeJS v23.11.0. Please let me know if you can reproduce the issue.

ok, I think found the issue, it's because the peer dependency set is still set to 2.29.4 in all packages, which still doesn't include the sendCallsSync function that the internal wagmi is looking for.

Usually a quick fix would be adding

"overrides": { "viem": "2.38.x" },

to your package.json

But I pushed a new commit to this PR and published new snapshots you can test:

🦋  New tag:  @lit-protocol/auth@0.0.0-20251020130647
🦋  New tag:  @lit-protocol/auth-helpers@0.0.0-20251020130647
🦋  New tag:  @lit-protocol/auth-services@0.0.0-20251020130647
🦋  New tag:  @lit-protocol/constants@0.0.0-20251020130647
🦋  New tag:  @lit-protocol/contracts@0.0.0-20251020130647
🦋  New tag:  @lit-protocol/e2e@0.0.0-20251020130647
🦋  New tag:  @lit-protocol/lit-client@0.0.0-20251020130647
🦋  New tag:  @lit-protocol/networks@0.0.0-20251020130647

I also created an example repo here and tested it with your env settings and it works:
LIT-Protocol/naga-sdk-npm-example#1

[CodeSandwich]

Yes, this fixes the issue! I'll attach this issue to the PR.

  "dependencies": {
    "@lit-protocol/lit-client": "=0.0.0-20251020130647",
    "@lit-protocol/networks": "=0.0.0-20251020130647"
  }

[Ansonhkg]

@CodeSandwich Awesome! Thanks for reporting this and making the SDK better!

[Ansonhkg]

Hi Igor, fyi. I just released new versions here:

#966

https://naga.developer.litprotocol.com/changelog