Could not use `optional chaining` in nuxt.config.ts

Describe the bug Using optional chaining in nuxt.config.ts causes run-time error.

 ERROR  Unexpected token . 

  const hello = fuga?.foo.bar;
  ^

  SyntaxError: Unexpected token .

To Reproduce See CodeSandbox

https://codesandbox.io/embed/nuxtnuxtjs-typescript-q064y?fontsize=14&hidenavigation=1&theme=dark

Expected behavior No error happens

Additional context To avoid this error, change target property’s value of tsconfig.json into es2018 from esnext. https://github.com/TypeStrong/ts-node/issues/903#issuecomment-551265568

But the configuration displayed in the official document says that targe value is esnext. https://typescript.nuxtjs.org/guide/setup.html#configuration

[kevinmarrec]

@azawakh Wow thanks, it seems that babel plugins are not needed at all then, we can let TypeScript handles the transpilation of the features by specifying.

Only esnext seems buggy, es5 / es2018 / es2019 / es2020 work well.

I’m gonna remove Babel plugins and tell people to update their TypeScript configuration file in release so it works out of the box for build & runtime ouf of the box !

[kevinmarrec]

Closed by https://github.com/nuxt/typescript/commit/826234b5ff24a90e771d10b1029d1adabd8de6fb

Babel plugins will be removed (useless if using es2018 target) in next release later this day.