dist/hdkey.js (Maintainer Update: Critical bug in v0.6.1, now fixed with v0.6.2, please update!)
See original GitHub issueWith the new 0.6.1 release, this:
const hdkey = require('ethereumjs-wallet/hdkey');
Must be changed to:
const hdkey = require('ethereumjs-wallet/dist/hdkey');
Maybe that’s not what you intended? Even though your pkg.json main points at dist/
, a module reference like 'ethereumjs-wallet/hdkey'
only works if hdkey.js
is at the top-level of the package.
In the published package, you could include an hdkey.js
that’s a one-liner:
module.exports = require('./dist/hdkey.js');
However, you would need to reorg the sources that get transpiled by babel under src/
and update the build:dist
script accordingly.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:7
- Comments:18 (11 by maintainers)
Top Results From Across the Web
CRITICAL! Unable to process chain reorg / too many ... - GitHub
Unable to process chain reorg [bug]: CRITICAL! Unable to process chain reorg / too many witness items to fit into max message size...
Read more >Changelog | Meteor API Docs
Update postcss package to avoid issues with Browserslist and caniuse-lite . PR. minifier-js@2.7.5 : Update terser package due to security fixes and to...
Read more >pdf2json - npm
PDF file parser that converts PDF binaries to text based JSON, powered by porting a fork of PDF.JS to Node.js. Latest version: 3.0.2,...
Read more >npm Libraries 'colors' and 'faker' Sabotaged in Protest by their ...
Popular npm open source libraries, colors.js, and faker.js were sabotaged by their own maintainer. What does that mean for open source ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@axic @holgerd77 If a fix will be longer than a few days, it might be better to republish
0.6.0
as0.6.2
. This dependency breaking has been impacting a lot of packages.My current impulse is to put the original sources in a folder
src/
and then transpile to the root directory and do a PR on this, I think there are not too many paths to be changed in this regard, and then release asv0.6.2
.Anything speaking against this solution?