Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to parse source map from .../signing-key/lib.esm/browser-elliptic.js.map #1494

Closed
j1mmie opened this issue Apr 21, 2021 · 1 comment
Closed
Labels
bug Verified to be an issue. fixed/complete This Bug is fixed or Enhancement is complete and published.

Comments

@j1mmie
Copy link

j1mmie commented Apr 21, 2021

I have a project that uses yarn and webpack, and includes ethers as a dependency. When I start the project via yarn, I see this warning:

WARNING in ./node_modules/@ethersproject/signing-key/lib.esm/elliptic.js
Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from '/Users/jimmie/Projects/Lazy3d/frontend/node_modules/@ethersproject/signing-key/lib.esm/browser-elliptic.js.map' file: Error: ENOENT: no such file or directory, open '/Users/jimmie/Projects/Lazy3d/frontend/node_modules/@ethersproject/signing-key/lib.esm/browser-elliptic.js.map'
 @ ./node_modules/@ethersproject/signing-key/lib.esm/index.js 2:0-32 11:21-23
 @ ./node_modules/@ethersproject/transactions/lib.esm/index.js 9:0-80 39:22-38 43:26-42
 @ ./node_modules/@ethersproject/providers/lib.esm/etherscan-provider.js 13:0-60 33:25-38
 @ ./node_modules/@ethersproject/providers/lib.esm/index.js 7:0-57 55:8-25 66:0-80:12
 @ ./src/app/users/EnsUser.ts 53:0-62 67:39-57
 @ ./src/app/users/UserFactory.ts 1:0-32 6:8-25 7:19-26
 @ ./src/app/index.ts 43:0-46 109:36-47

I've determined that if I change this line:

//# sourceMappingURL=browser-elliptic.js.map

to simply:

//# sourceMappingURL=elliptic.js.map

the warning disappears.

I don't really know enough about this project to know if the line is incorrect as is, or if I've configured something on my end that is misinterpreting it. Also not really sure how this lib.esm folder is getting generated. Any thoughts would be appreciated, happy to submit a fix if I can get some guidance. I suspect change that line is not the appropriate way to fix it.

Thanks!

@ricmoo ricmoo added investigate Under investigation and may be a bug. on-deck This Enhancement or Bug is currently being worked on. labels Apr 22, 2021
ricmoo added a commit that referenced this issue Oct 16, 2021
@ricmoo ricmoo removed the investigate Under investigation and may be a bug. label Oct 16, 2021
@ricmoo
Copy link
Member

ricmoo commented Oct 20, 2021

Fixed in 5.5.0.

It was a missing /m in the regex of the aliasing script. :s

Thanks! :)

@ricmoo ricmoo closed this as completed Oct 20, 2021
@ricmoo ricmoo added bug Verified to be an issue. fixed/complete This Bug is fixed or Enhancement is complete and published. and removed on-deck This Enhancement or Bug is currently being worked on. labels Oct 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Verified to be an issue. fixed/complete This Bug is fixed or Enhancement is complete and published.
Projects
None yet
Development

No branches or pull requests

2 participants