chore(build): fix eslint pattern

[dhruvdutt]

What kind of change does this PR introduce?

Did you add tests for your changes?

If relevant, did you update the documentation?

Summary

Does this PR introduce a breaking change?

Other information

[dhruvdutt]

Should we ignore the test folder? It's currently in eslintignore.

webpack-cli/.eslintignore

Line 3 in cd890a8

test

[ematipico]

Why we don't want to lint the tests? Sounds odd to me

[dhruvdutt]

You're right. There is no reason to ignore the test. Fixed it.

[dhruvdutt]

This is needed because eslint-disable can't work on some files like:

2:1  error  Parsing error: Unexpected token }

[ematipico]

But that's a SyntaxError. It would bomb an error anyway

[dhruvdutt]

Yeah. This is error checking test. 😅

webpack-cli/test/binCases/errors/parse/stdin.js

Lines 10 to 13 in cd890a8

	expect(stdout[5]).toContain("[failed]");
	expect(stdout[5]).toContain("[1 error]");
	expect(stdout[7]).toContain("ERROR in ./index.js");
	expect(stdout[8]).toContain("Module parse failed:");

[ematipico]

Thanks for the clarification!

[dhruvdutt]

This should be ignored from linters, right?

[ematipico]

Yes

[ematipico]

Looks good to me! So now we have eslint properly set :)