Gulp `"options"` vs Grunt `"extra"` … parity?

[mysterycommand]

I've used grunt-modernizr before, but on my current project we're using Gulp, and I'd like to use this project to the same end. However, the configuration looks different to me and the README on customizr isn't helping too much. On customizr the configuration options look like:

{
  options: [
    'setClasses',
    'addTest',
    'html5printshiv',
    'testProp',
    'fnBind'
  ]
}

… but I'm not sure how (or if) these options map to Modernizr's "Extra" section. It was a little clearer with grunt-modernizr:

{
  extra: {
    shiv: true,
    printshiv: false,
    load: true,
    mq: false,
    cssclasses: true
  }
}

… I had a configuration I liked in grunt-modernizr. What's the easiest way to re-create that configuration with the Gulp version? Thanks!

[olafgleba]

I guess

{
  options: [
    'setClasses'
  ]
}

actually should do the trick as a complement to cssclasses for example. But options doesn't work for me at all. It seems it is still not implemented (on modernizr v3 itself). Because when you do a custom build on the modernizr(v3) site itself it also leads to nothing as these options does not get into the generated source.