-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Unable to build ember from master #17678
Comments
Error log: https://dpaste.de/j3ZU |
Offending commit appears to be e90aee2 |
Fixes the build as reported in emberjs#17678
@rwjblue @stefanpenner I ran into this as well tonight, seems related to the bump of hash-for-dep from 1.2.3 to 1.4.7. I opened a hacky quick fix for Ember in #17679. |
Thanks for reporting! Will dig in to see what’s going on... |
I have an idea what the issue is. And with the reproduction it should be easy to tackle. |
I don't know if this is related but when using my local
Steps:
|
@ppcano You need to run |
hashForDep with invalid input, would not error rather would produce a checksum. So restoring this for now, although we should remove in the next major version. One deviation from the old behavior is to ensure the all garbage input doesn’t produce the same hash, rather it will get a hash based on inputs provided. Context: * emberjs/ember.js#17679 * emberjs/ember.js#17678
@ppcano that doesn't seem related |
hashForDep with invalid input, would not error rather would produce a checksum. So restoring this for now, although we should remove in the next major version. One deviation from the old behavior is to ensure the all garbage input doesn’t produce the same hash, rather it will get a hash based on inputs provided. Context: * emberjs/ember.js#17679 * emberjs/ember.js#17678
I'm trying to build ember using
yarn install
andyarn build
, and am running into the following error:A paste of my process:
https://dpaste.de/Ne8h
Node version: v10.15.0
Yarn version: v1.13.0
Operating system: macos 10.14.3
The issue was replicated on another machine by @efx on discord.
The text was updated successfully, but these errors were encountered: