Closed dylang closed 10 years ago
Yeah, I'm going to fix and release 0.4.6 shortly.
@dylang can you npm update
and see if it picks up grunt-legacy-log@0.1.1?
If this works I won't need to update Grunt, I'll just tell people experiencing the problem to update.
Thanks for the quick fix!
:heart: :heart: :heart:
@dylang did npm update
fix it, or did you have to do something more severe?
npm update
fixed the problem.
Before
grunt 0.4.5
you could do this:grunt 0.4.5
switched togrunt-legacy-log
which changed howok
is exposed in such a way that callinglog()
in the above example, the context is lost and the code ingrunt-legacy-log
that tries to usethis
will throw an exception.A fix for this is:
But I would argue this is an unexpected breaking change and not good artifact for the api to have.