"Module parse failed" running next dev in 8.1.1-canary.28

Bug report

Describe the bug

Running next dev in my project is causing a Module parse failed: Unexpected token error when trying to compile next/dist/client/next-dev.js:

Module parse failed: Unexpected token (19:6)
You may need an appropriate loader to handle this file type.
|
|
> import('./noop'); // Support EventSource on Internet Explorer 11
|
| if (!window.EventSource) {

To Reproduce

My babel configuration is:

{
  presets: [
    [
      'next/babel',
      {
        'preset-env': {
          useBuiltIns: 'usage',
        },
      },
    ],
    '@babel/preset-typescript'
  ],
  plugins: [
    ['@babel/plugin-proposal-decorators', { legacy: true }],
    ['@babel/plugin-proposal-class-properties', { loose: true }],
  ]
}

I can reproduce even when my next.config.js does not modify the webpack config.

Expected behavior

Compilation should succeed

System information

• Version of Next.js: 8.1.1-canary.28

Additional context

This is in a Yarn workspace–using monorepo, so the next package gets installed in a node_modules that’s a few directories up from where my source is.

[ijjk]

Or is just “try to shuffle your dependencies around until #6940 is implemented”

This seems to be the case for now, although we have prioritized #6940 I’m gonna close this issue in favor of the mentioned one, if you have any additional information that you think is helpful feel free to add it to that thread.

[ijjk]

Awesome thanks 🙏, by included I mean when you add the next/babel it already adds @babel/preset-typescript