Package subpath './lib/utils' is not defined by "exports"

[kakui-lau]

Ethers Version

6.5.1

Search Terms

No response

Describe the Problem

v16.18.1
Mac
When importing package runtime, Package subpath '/ Lib/utils' is not defined by "exports"

Code Snippet

`
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/utils' is not defined by "exports" in /Users/kakui/projects/test/packages/chaindata/node_modules/ethers/package.json
    at new NodeError (node:internal/errors:387:5)
    at throwExportsNotFound (node:internal/modules/esm/resolve:365:9)
    at packageExportsResolve (node:internal/modules/esm/resolve:649:3)
    at resolveExports (node:internal/modules/cjs/loader:522:36)
    at Function.Module._findPath (node:internal/modules/cjs/loader:562:31)
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:971:27)
    at Function.Module._resolveFilename.sharedData.moduleResolveFilenameHook.installedValue [as _resolveFilename] (/Users/kakui/projects/OB_BlockExplore/node_modules/@cspotcode/source-map-support/source-map-support.js:811:30)
    at Function.Module._load (node:internal/modules/cjs/loader:833:27)
    at Module.require (node:internal/modules/cjs/loader:1057:19)
    at require (node:internal/modules/cjs/helpers:103:18) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}
npm ERR! Lifecycle script `dev` failed with error: 
npm ERR! Error: command failed 
npm ERR!   in workspace: [email protected] 
npm ERR!   at location: /Users/kakui/projects/test/packages/
`

Contract ABI

No response

Errors

No response

Environment

node.js (v12 or newer)

Environment (Other)

No response

[ricmoo]

What are you trying to do? That path is not exported, so the error seems correct?

[kakui-lau]

What are you trying to do? That path is not exported, so the error seems correct?

I want to run the program, but I am prompted with this error. It seems that there are some issues with the export in the ethers package

[ricmoo]

What makes you think that is an ethers error though? Ethers doesn’t have that path in its package.json. It looks like it might be coming from a package in spotcode?

[kakui-lau]

What makes you think that is an ethers error though? Ethers doesn’t have that path in its package.json. It looks like it might be coming from a package in spotcode?

Because I am not running the package containing ether packages, it can run normally. However, this error occurred after the package was introduced. Sorry, I am not very sure if it is the problem with this package

[ricmoo]

I don't think this issue is related to Ethers. I'm moving it to discussions though, if you can provide more information though, it can be moved back as an issue.

[forshtat]

@kakui-lau Just had the same issue. For the record, in my case this was caused by having the following import:
import { parseEther } from 'ethers/lib/utils'

...and was solved by replacing it with
import { parseEther } from 'ethers'

[quThinh]

Does anyone have answer for this question yet?

[ricmoo]

Can you provide reproduction steps? There should be no lib path in v6.

[quThinh]

I found out that utils now is not a part of ethers v6 anymore. I see that hardhat-deploy lib and @openzeppelin/hardhat-upgrades lib is using "ethers/lib/utils" import. So maybe this is where the error came from. Should I do anything to fix this error

[ricmoo]

Everything in ethers is now available on the root object, including utils, since tree shaking works now. :)

Recent versions of hardhat should be using v6, so I guess Open Zeppelin needs to be updated?

[quThinh]

Or may be it's hardhat? Because I saw on npm, it still depent on ether v5