component.json: Update deps

[stephenmathieson]

No description provided.

[stephenmathieson]

@pirxpilot thoughts? you seem to be maintaining this

[pirxpilot]

sorry -- somehow it got lost in my notifications' stream

[pirxpilot]

Released 0.3.2
That said, I am thinking we should just stop pinning deps in component.json files - it quickly becomes unmanageable and component installer (for component 0.x) pretty much ignores the versions anyway (it installs whatever version is first referenced).
I use component-shrinkwrap to manage versions.

[stephenmathieson]

I'm using component@1 for now (bitbucket support ;)), so pinning lets me trim down my dependency tree. I can always fork if you don't want to merge/release tedious stuff like this though.

[stephenmathieson]

Also, thanks! Haha

[pirxpilot]

No worries. I'd rather have core components play nice with the latest version of the builder.
It's just that I was under (apparently misguided) impression that we won't need version pinning for 1.x ;-)
Well, one of these days I'll have to upgrade my projects. Not looking forward to it...

[stephenmathieson]

Nope you're absolutely right; we have 1.x, etc. I just don't want to loose support for component v0 until v1 is stable and everyone has had a chance to update.

On Jul 26, 2014, at 8:03 AM, pirxpilot notifications@github.com wrote:

No worries. I'd rather have core components play nice with the latest version of the builder.
It's just that I was under (apparently misguided) impression that we won't need version pinning for 1.x ;-)
Well, one of these days I'll have to upgrade my projects. Not looking forward to it...

—
Reply to this email directly or view it on GitHub.