Newline between grouped imports

I want my imports to not have any new lines between them. I followed the instructions here and am using the following rules:

.eslintrc.js:

module.exports = {
  ...
  rules: {
    ...
    'import/first': 'error',
    'import/newline-after-import': 'error',
    'simple-import-sort/imports': [
      'error',
      {
        groups: [
          [
            "^react",
            "^@?\\w",
            "^(main|core|arc-storybook|viz|design-system|placement|reporting|onboarding)(/.*|$)",
            "^\\u0000",
            "^\\.\\.(?!/?$)",
            "^\\.\\./?$",
            "^.+\\.s?css$",
          ],
        ],
      }
    ],
  },
};

I have a sample component, as seen here:

import React from 'react';
import { EuiButton } from '@elastic/eui/src/components/button/button';
import x from './bar';

const Foo: React.FC = () => <EuiButton>Click Me</EuiButton>;

export default Foo;

but when I run prettier-eslint --write src/Foo.tsx, it adds a space between the second and third import:

import React from 'react';
import { EuiButton } from '@elastic/eui/src/components/button/button';

import x from './bar';

const Foo: React.FC = () => <EuiButton>Click Me</EuiButton>;

export default Foo;

How can I make sure that a new line is not added between the second and third import statement? Thanks!

[jimmy-e]

Ok great, thanks for the help!

Fixed eslint:

module.exports = {
  parser: 'babel-eslint',
  plugins: ['simple-import-sort'],
  rules: {
    'simple-import-sort/imports': [
      'error',
      {
        groups: [
          [
            "^react",
            "^@?\\w",
            "^(main|core|arc-storybook|viz|design-system|placement|reporting|onboarding)(/.*|$)",
            "^\\u0000",
            "^\\.\\.(?!/?$)", "^\\.\\./?$",
            "^\\./(?=.*/)(?!/?$)", "^\\.(?!/?$)", "^\\./?$",
            "^.+\\.s?css$",
          ],
        ],
      }
    ],
  },
};

[jimmy-e]

Apologies @lydell , I should have done that first. I have reduced the eslint to as simple a config as possible but am still getting the same issue; maybe it is an issue with TypeScript. I will try duplicating the repo but without TypeScript and look into this further and will get back to you in a day or so.