Skip to content
This repository has been archived by the owner on Jun 17, 2021. It is now read-only.

Fix browserify issue #119

Merged
merged 1 commit into from
Feb 26, 2018
Merged

Fix browserify issue #119

merged 1 commit into from
Feb 26, 2018

Conversation

holgerd77
Copy link
Member

@holgerd77 holgerd77 commented Feb 20, 2018

Same as in ethereumjs-block, see ethereumjs/ethereumjs-block#40.

Also fixes #118.

@holgerd77 holgerd77 force-pushed the fix-browserify-issue branch from d0daf4b to ba1ae59 Compare February 20, 2018 20:38
@coveralls
Copy link

coveralls commented Feb 20, 2018

Coverage Status

Coverage remained the same at 99.17% when pulling ba1ae59 on fix-browserify-issue into cf511cc on master.

@@ -17,18 +17,6 @@
"build:dist": "babel index.js --source-root ./ -d ./dist",
"build:docs": "documentation build ./index.js --github --sort-order='alpha' -f md > ./docs/index.md"
},
"browserify": {
Copy link
Contributor

@Silur Silur Feb 20, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe leave this as a script for containers etc are not forced to have a global browserify in PATH and only npm ... scripts can access the .bin dir to hook up a dependency?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this was never meant to be used for browserify itself but is just used internally for karma testing. Or am I wrong here?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes there is no browserify in the build for this module - it's only for karma

@alanshaw
Copy link

Ping! Can has merge+release plz?

@holgerd77 holgerd77 merged commit ea95661 into master Feb 26, 2018
@holgerd77 holgerd77 deleted the fix-browserify-issue branch February 26, 2018 10:48
@holgerd77
Copy link
Member Author

@alanshaw Sorry, forgot about that one, just merged, will prepare a minor release asap.

@alanshaw
Copy link

thank you @holgerd77

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

An in-range update of standard is breaking the build 🚨
4 participants