Long line-length require statements are awkwardly formatted.

It seems that there’s no concept of keeping require statements and its params as one unit. It’s not very often that you’ll get an extremely long string to pass in to the require() parens. There should be a preference for keeping the require('./something') as one unit.

If I run prettier on this:

const { one, two, thee, four, five, six, seven, eight, nine, ten } = require('./my-utils');

I get this:

const { one, two, thee, four, five, six, seven, eight, nine, ten } = require(
  "./my-utils"
);

When it should be:

const { one, two, thee, four, five, six, seven, eight, nine, ten }
  = require('./my-utils');

or:

const { 
  one, 
  two, 
  thee, 
  four, 
  five, 
  six, 
  seven, 
  eight, 
  nine, 
  ten } = require('./my-utils');

[jlongster]

I’d say this is the expected behavior for “normal” expressions. Trying to figure out which one is bigger could possibly done, but we need to be really careful how many combinations of styles we try to detect before performance becomes a serious issue.

Also, I’d prefer for the format to be as consistent as possible. The above case, even if it’s slightly awkward in rare cases, is consistent.

What we could do is specialize the require pattern specifically. This is what I talked about in Respecting Patterns. It’s a very common pattern to destructure a large amount of imported properties, so we could specifically break it differently.

[vjeux]

#841 fixes it.