Sindre Sorhus

No, I meant, it should have fixed it to: ```js Object.assign(stream, { isTTY: true, columns, rows }); ```

> Is there anything preventing adding object-curly-newline, though? PR welcome :)

> I think they should only be allowed for simple functions with implicit returns Why? I prefer arrow functions for everything as they're lexically scoped (no dumb implicit `this`) and...

Yes, I like to figure out a good default we can enforce for this too. I don't feel super strongly either way, just slightly prefer arrow functions. Also nested function...

I agree that ES2015 exports should use a normal function. This: ``` js export function foo() {} ``` Looks better than this: ``` js export const foo = () =>...

I agree, it should only apply to functions.

In your example, spreading makes more sense, but spreading does not allow decided the `this` context.

We could potentially add support for `.apply` in https://github.com/sindresorhus/eslint-plugin-unicorn/blob/main/docs/rules/prefer-spread.md

// @Richienb

@AndrewMSHowe Can you try running `$ npx xo` in your project?