Please remove grunt from peerDependencies from package.json

[paladox]

Please fix peerDependencies since it is failing grunt 1.0.0

Update
"peerDependencies": {
"grunt": ">=0.4.x"
},

to

"peerDependencies": {
"grunt": ">=0.4.0"
},

@dignifiedquire or @vladikoff Please could you do it since I doint want to sign the cla.

[vladikoff]

@paladox this is already done, having the "grunt": ">=0.4.x", is good enough.

In your project you are using [email protected] that wants [email protected] which still had "grunt": "0.4.x"

[vladikoff]

See 0.12.1 version https://github.com/karma-runner/grunt-karma/blob/v0.12.1/package.json#L47 and compare it with master

[vladikoff]

@paladox see http://gruntjs.com/blog/2016-02-11-grunt-1.0.0-rc1-released#peer-dependencies

[paladox]

Thanks ive asked for this to be released as a 0.12.2 update.

[paladox]

@vladikoff Actually see gruntjs/grunt-contrib-watch@1f198f6

Still causing

19:34:58 npm ERR! peerinvalid The package grunt does not satisfy its siblings' peerDependencies requirements!
19:34:58 npm ERR! peerinvalid Peer [email protected] wants grunt@>=0.4.0
19:34:58 npm ERR! peerinvalid Peer [email protected] wants grunt@>=0.4.0
19:34:58 npm ERR! peerinvalid Peer [email protected] wants [email protected]
19:34:58

Now its one module less since updating watch which had peer but removed it in 1.x update.

[vladikoff]

@paladox Yeah you can both remove and keep it. Some developers prefer to keep this setting.

[paladox]

@vladikoff do you suggest to keep it, how would we support 1.0 of grunt.

[paladox]

Please

[vladikoff]

@vladikoff do you suggest to keep it, how would we support 1.0 of grunt.

Plugins that will have >=0.4.0 as a peerDep will just work:

(rc1 is currently failing but that's npm's fault)

[paladox]

@vladikoff Oh ok thanks. So its grunt that the problem. Should we file a task with them.

[paladox]

Ive reported it here gruntjs/grunt#1488

[dignifiedquire]

New version released which should fix this

[paladox]

Thanks.