Veeck
Veeck
Moved to grunt-modernizr since that is what you are using, Which version of grunt / grunt-modernizr are you using?
(The failing modernizr build is unrelated)
Could you try the latest master branch of this repo where we updated all the dependencies? Just use "grunt-modernizr": "https://github.com/Modernizr/grunt-modernizr#master" in your package.json (and do a npm install) to try...
(I dont have publishing rights on npm so the latest v2 cannot be published yet). Also: which node and grunt versions are you using?
Hrmpf... Is your grunt file somewhere publicly visible for me to check out? And what tests are expected for it to be found?
I am a little baffled now... Tried out grunt-config on my project and it worked fine with this dependencies: ``` "grunt": "^1.0.3", "grunt-modernizr": "https://github.com/Modernizr/grunt-modernizr.git", ``` and this config ``` module.exports...
You're right, there is indeed that one generate call (I can only say as an excuse that i am a little under the weather these days). Could you try if...
@jamie-l-robertson next try: coudl you rename your task from modenrizr to something else since grunt.modernizr itself defines a "mnodernizr"-grunt task? (a shot in the dark sicne I dont know if...
@jamie-l-robertson so renaming the task didnt help to solve your problem?
hi @devprojectsapps unfortunatly I cannot help you with these old and outdated versions of grunt-modernizr and modernizr. Is upgrading to v2 of grunt-modernizr (and therefor v3 of modernizr too) an...