Prettier on the Jest repo

Not sure if this issue is valid by itself, but I tried out prettier on the Jest repo and there are a number of issues that I found. Feel free to close this issue if it isn’t detailed enough or you aren’t planning on fixing any of these.

I ran:

node_modules/.bin/prettier --write "packages/*/src/**.js" --single-quote --trailing-comma --bracket-spacing=false --parser=flow

on the jest repo and got a bunch of lines that are longer than 80 characters. Examples:

    return chalk.bold('No tests found') +
      '\n' +
      (data.total
        ? `  ${pluralize('file', data.total || 0, 's')} checked.\n` +
            statsMessage
        : `No files found in ${config.rootDir}.\n` +
            `Make sure Jest's configuration does not exclude this directory.\n` +
            `To set up Jest, make sure a package.json file exists.\n` +
            `Jest Documentation: facebook.github.io/jest/docs/configuration.html`);

or:

const JASMINE_IGNORE = /^\s+at(?:(?:.*?vendor\/|jasmine\-)|\s+jasmine\.buildExpectationResult)/;
const STACK_TRACE_IGNORE = /^\s+at.*?jest(-.*?)?(\/|\\)(vendor|build|node_modules|packages)(\/|\\)/;

[cpojer]

For years I’ve been using this style (cc @thymikee):

array.forEach(
  item => doSomethingWith(item),
);

but prettier prefers:

array.forEach(item =>
  doSomethingWith(item),
);

which seems less readable in the common case.

[cpojer]

Happy to start using it on parts of the codebase, though: https://github.com/facebook/jest/pull/2975