Lavaclient v5 dependency issue with pnpm10

hey! haven't been here in a while;

Done in 1m 40.1s using pnpm v10.8.0

> [email protected] build D:\Documents\GitHub\Quaver
> rimraf dist/ && genversion --es6 --semi src/lib/util/version.ts && tsc && tsc-alias


> [email protected] start D:\Documents\GitHub\Quaver
> node .

node:internal/modules/esm/resolve:314
  return new ERR_PACKAGE_PATH_NOT_EXPORTED(
         ^

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './ReadonlyArray' is not defined by "exports" in D:\Documents\GitHub\Quaver\node_modules\.pnpm\@[email protected][email protected][email protected]\node_modules\effect\package.json
    at exportsNotFound (node:internal/modules/esm/resolve:314:10)
    at packageExportsResolve (node:internal/modules/esm/resolve:662:9)
    at resolveExports (node:internal/modules/cjs/loader:638:36)
    at Function._findPath (node:internal/modules/cjs/loader:743:31)
    at Function._resolveFilename (node:internal/modules/cjs/loader:1230:27)
    at Function._load (node:internal/modules/cjs/loader:1070:27)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
    at Module.require (node:internal/modules/cjs/loader:1335:12)
    at require (node:internal/modules/helpers:136:16) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

Node.js v22.13.1
 ELIFECYCLE  Command failed with exit code 1.

Done in 1m 40.1s using pnpm v10.8.0

> [email protected] build D:\Documents\GitHub\Quaver
> rimraf dist/ && genversion --es6 --semi src/lib/util/version.ts && tsc && tsc-alias


> [email protected] start D:\Documents\GitHub\Quaver
> node .

node:internal/modules/esm/resolve:314
  return new ERR_PACKAGE_PATH_NOT_EXPORTED(
         ^

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './ReadonlyArray' is not defined by "exports" in D:\Documents\GitHub\Quaver\node_modules\.pnpm\@[email protected][email protected][email protected]\node_modules\effect\package.json
    at exportsNotFound (node:internal/modules/esm/resolve:314:10)
    at packageExportsResolve (node:internal/modules/esm/resolve:662:9)
    at resolveExports (node:internal/modules/cjs/loader:638:36)
    at Function._findPath (node:internal/modules/cjs/loader:743:31)
    at Function._resolveFilename (node:internal/modules/cjs/loader:1230:27)
    at Function._load (node:internal/modules/cjs/loader:1070:27)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
    at Module.require (node:internal/modules/cjs/loader:1335:12)
    at require (node:internal/modules/helpers:136:16) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

Node.js v22.13.1
 ELIFECYCLE  Command failed with exit code 1.

we're currently seeing this issue after running pnpm i with pnpm 10 (pnpm 8 doesn't have this issue) - i believe there's some issue with the @effect/schema dep, although i wasn't able to dig too deep into it

8 Replies

viztea•2w ago

does it work with pnpm 9? i'll likely update @effect/schema soon anyways it'll probably be a breaking change for anybody who uses it for type-safe track user data though

maxOP•2w ago

good question let me see

Done in 2m 47.9s using pnpm v9.15.9

> [email protected] build D:\Documents\GitHub\Quaver
> rimraf dist/ && genversion --es6 --semi src/lib/util/version.ts && tsc && tsc-alias


> [email protected] start D:\Documents\GitHub\Quaver
> node .

node:internal/modules/esm/resolve:314
  return new ERR_PACKAGE_PATH_NOT_EXPORTED(
         ^

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './ReadonlyArray' is not defined by "exports" in D:\Documents\GitHub\Quaver\node_modules\.pnpm\@[email protected][email protected][email protected]\node_modules\effect\package.json
    at exportsNotFound (node:internal/modules/esm/resolve:314:10)
    at packageExportsResolve (node:internal/modules/esm/resolve:662:9)
    at resolveExports (node:internal/modules/cjs/loader:638:36)
    at Function._findPath (node:internal/modules/cjs/loader:743:31)
    at Function._resolveFilename (node:internal/modules/cjs/loader:1230:27)
    at Function._load (node:internal/modules/cjs/loader:1070:27)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
    at Module.require (node:internal/modules/cjs/loader:1335:12)
    at require (node:internal/modules/helpers:136:16) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

Node.js v22.13.1
 ELIFECYCLE  Command failed with exit code 1.

Done in 2m 47.9s using pnpm v9.15.9

> [email protected] build D:\Documents\GitHub\Quaver
> rimraf dist/ && genversion --es6 --semi src/lib/util/version.ts && tsc && tsc-alias


> [email protected] start D:\Documents\GitHub\Quaver
> node .

node:internal/modules/esm/resolve:314
  return new ERR_PACKAGE_PATH_NOT_EXPORTED(
         ^

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './ReadonlyArray' is not defined by "exports" in D:\Documents\GitHub\Quaver\node_modules\.pnpm\@[email protected][email protected][email protected]\node_modules\effect\package.json
    at exportsNotFound (node:internal/modules/esm/resolve:314:10)
    at packageExportsResolve (node:internal/modules/esm/resolve:662:9)
    at resolveExports (node:internal/modules/cjs/loader:638:36)
    at Function._findPath (node:internal/modules/cjs/loader:743:31)
    at Function._resolveFilename (node:internal/modules/cjs/loader:1230:27)
    at Function._load (node:internal/modules/cjs/loader:1070:27)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
    at Module.require (node:internal/modules/cjs/loader:1335:12)
    at require (node:internal/modules/helpers:136:16) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

Node.js v22.13.1
 ELIFECYCLE  Command failed with exit code 1.

unfortunately not

viztea•2w ago

ok ill look at the changelog

maxOP•2w ago

sick, thanks

viztea•6d ago

i may have completely forgot about this i did look at the change log though and didn't see anything that would've broken it @max I assume this isn't that big of a deal for you?

maxOP•5d ago

hm it's forcing us to stay on pnpm 8, would it be fixed in v5's full release?

viztea•5d ago

probably

maxOP•5d ago

great, for now i'm forcing pnpm 8 but when it gets fixed eventually i'll bump us back to pnpm 10

Gaming

Programming

Lavaclient v5 dependency issue with pnpm10

Did you find this page helpful?