Package.json in the generator pulls a specific version of eslint through grunt-eslint https://github.com/cfpb/generator-cf/blob/master/app/templates/_package.json#L28 (0.19.0), however, the front-end repo has been updated to work with the latest version (0.21.0). Either generator-cf should pull in the latest grunt-eslint with "grunt-eslint": "latest" (I believe that's the syntax?) or, safer, it should pull a specific version of the lint file with that's pegged against the version of eslint installed, e.g. pulling in https://github.com/cfpb/front-end/blob/53b7d38df6e91d03bd7e4839d489fccd680a58fc/.eslintrc ... not pegging the lint file and the eslint version installed against each other always risks that one or the other introduces breaking changes as the versions increment (as is currently the case in generator-cf).
Package.json in the generator pulls a specific version of eslint through grunt-eslint https://github.com/cfpb/generator-cf/blob/master/app/templates/_package.json#L28 (0.19.0), however, the front-end repo has been updated to work with the latest version (0.21.0). Either generator-cf should pull in the latest grunt-eslint with
"grunt-eslint": "latest"(I believe that's the syntax?) or, safer, it should pull a specific version of the lint file with that's pegged against the version of eslint installed, e.g. pulling inhttps://github.com/cfpb/front-end/blob/53b7d38df6e91d03bd7e4839d489fccd680a58fc/.eslintrc... not pegging the lint file and the eslint version installed against each other always risks that one or the other introduces breaking changes as the versions increment (as is currently the case in generator-cf).