No ESLint configuration found.

[GaryB432]

I generated my generator and added a single file karma-conf.js right after dummyfile.txt. Now when I run npm test I get the error mentioned in the subject. A Typescript developer, I indeed do not have any ESLint configurations anywhere on my computer. Does the generator-generator generate a generator with like a peer dependency on that? Or what might I be doing wrong?

test/app.js

...
    assert.file([
      'dummyfile.txt',
      'karma-conf.js'
    ]);
...

generators/app/index.js

...
  writing: function () {
    this.fs.copy(
      this.templatePath('dummyfile.txt'),
      this.destinationPath('dummyfile.txt')
    );
    this.fs.copy(
      this.templatePath('karma-conf.js'),
      this.destinationPath('karma-conf-js')
    );
  },
...

versions

+-- chalk@1.1.3
+-- eslint@3.18.0
+-- eslint-config-xo-space@0.15.0
+-- gulp@3.9.1
+-- gulp-coveralls@0.1.4
+-- gulp-eslint@3.0.1
+-- gulp-exclude-gitignore@1.1.1
+-- gulp-istanbul@1.1.1
+-- gulp-line-ending-corrector@1.0.1
+-- gulp-mocha@3.0.1
+-- gulp-nsp@2.4.2
+-- gulp-plumber@1.1.0
+-- yeoman-assert@2.2.3
+-- yeoman-generator@1.1.1
+-- yeoman-test@1.6.0
`-- yosay@1.2.1

Thanks for checking!

[mischah]

It’s a regression caused by updating gulp-eslint with 2617144 which also causes failing builds on travis.

The issue is discussed over here: adametry/gulp-eslint#186

I’m going to investigate 🏃

[mischah]

@SBoudrias I fixed the issue regarding the code base of generator-generator by tweaking the gulpfile.js. See #184.

But I can’t fix the issue in the generated gulpfile.js which causes the trouble in the generated generator since the file is provided by generator-node. Because gulp is gone since yeoman/generator-node@0c28bcb

Any chance to release generator-node v2 anytime soon?

@GaryB432 You can fix that in your generated generator by replacing:

.pipe(eslint())

with:

.pipe(eslint({baseConfig: {extends: 'eslint:recommended'}}))

in the generated gulpfile.js

[GaryB432]

Thanks.. we're making some progress.. Now my template js is violating no-undef with 'require' is not defined. and others. What's the trick for defining that? I guess I don't really want to disable that rule. Sorry for bothering your issues list with ESLint noob questions.

[SBoudrias]

@GaryB432 Try setting env: {node: true}

[mischah]

I’m going to fix that now that we have generator-node v2.0.0

[GaryB432]

Looking forward to studying that commit so I can learn about the dependency on generator-node. Generators are cool. 💪