Module parse failed: Unexpected token When adding auth-passport package and creating strategy

Bug report

Describe the bug

A clear and concise description of the bug.

To Reproduce

Steps to reproduce the behaviour. Please provide code snippets or a repository:

1. Create the starter project
2. Add auth-passport package
3. Create Google Auth strategy
4. Go to adminUI

ERROR in <user folder>/node_modules/@keystonejs/auth-passport/node_modules/@keystonejs/app-admin-ui/client/components/ListTable.js 102:5
Module parse failed: Unexpected token (102:5)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
 // Functional Components
> type SortLinkProps = {
handleSortChange: Function,
active: boolean,

The same Error appears for a multitude of files

System information

• OS: Ubuntu
• Browser:Firefox

Additional context

Add any other context about the problem here.

[zenflow]

However, it’s more accurate to say that only password auth is currently supported in the admin UI. Other auth strategies still work when using the GraphQL endpoint.

@molomby Isn’t it kind of odd that passport auth is not supported by AdminUIApp, but it is supported by GraphQLApp, when auth strategy is an option only given to AdminUIApp (not GraphQLApp)?

const apps = [
  new GraphQLApp(),
  new AdminUIApp({ authStrategy: passportAuthStrategy }),
];

Probably “auth strategies” should have been independent “apps” to compose with your graphql app, admin ui app, etc. I would actually be super excited to collaborate and work on these new apps (app-password-auth, app-passport-auth) if there is interest in going that way.

[zenflow]

OK I opened issue #2658 because I think this “make AdminUIApp work with passport auth” stuff may be off topic of the original issue.

@molomby Would you be at all able to review my changes in PR #2657 (which include making the Admin UI support passport auth)?