Closed duizendnegen closed 8 years ago
Your own tests are unhappy :)
I'm not sure this is optimal, this makes revision-data a rather strict dependency ... what if a different plugin some day provides the same data? then the ordering might break
losing my license to code
coughs of course I always do npm test
locally before pushing
I agree - we've discussed managing dependencies a bit in our f2f in London, and have decided not to release 1.0 until we have figured out a good way to deal with it - this was the consensus of the current way to move forward, but feel free to give input if you see a different direction.
didBuild makes more sense conceptually, since it is "the thing to do after building" and not "the thing to do before uploading". Ensuring it does run after revision data is available is by requesting the ordering in ember-cli-deploy-revision-data.