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

Upgrade to [email protected] to fix frozen error #2

Merged
merged 1 commit into from
Jul 17, 2015

Conversation

lejeunerenard
Copy link

I am submitting this as a PR since your fork doesn't have issues.

When I run the tests with node v0.12.5, I get the following

Warning: Cannot define property:48, object is not extensible. Use --force to continue.

I believe node changed how it handles Object.freeze(). So I managed to trace it back to the temporary dependency which has a new release to fix the error.

Turns out someone else figured it out and submitted a fix chrisgladd#30. Since people use your fork for the bower fix, if you could merge @OlenDavis's PR that'd be awesome.

fixes chrisgladd#41

When I run the tests with node v0.12.5, I get the following

    Warning: Cannot define property:48, object is not extensible. Use
    --force to continue.

I believe node changed how it handles Object.freeze(). I managed to
trace it back to the temporary dependency which has a new release to
fix the error.
clarkeadg added a commit that referenced this pull request Jul 17, 2015
@clarkeadg clarkeadg merged commit 8230d65 into clarkeadg:master Jul 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot define property:33, object is not extensible
2 participants