Null coalescing operator and optional chaining not handled in main build

Describe the bug Hi,

Thanks for this plugin. “New” syntax like “Null coalescing operator” and “optional chaining” make the main build fail.

error  in ./src/electron/main.ts

Module parse failed: Unexpected token (14:25)
File was processed with these loaders:
 * ./node_modules/ts-loader/index.js
You may need an additional loader to handle the result of these loaders.
|         { scheme: 'app', privileges: { secure: true, standard: true } },
|     ]);
>     console.log('false' ?? 'true');
|     await registerAppEventsListeners(app);
|     createMenu();

 @ multi ./src/electron/main.ts

 error  in ./src/electron/main.ts

Module parse failed: Unexpected token (15:20)
File was processed with these loaders:
 * ./node_modules/ts-loader/index.js
You may need an additional loader to handle the result of these loaders.
|     ]);
|     const foo = {};
>     console.log(foo?.bar || 'fff');
|     await registerAppEventsListeners(app);
|     createMenu();

 @ multi ./src/electron/main.ts

To Reproduce Steps to reproduce the behavior: Add any of them in your main file.

console.log('foo' ?? 'bar');
console.log(foo?.bar);

Expected behavior Build ok with transpilation needed for the electron version (so none I think).

Environment (please complete the following information):

• custom config for vcp-electron-builder:

   mainProcessFile: path.join(__dirname, 'main.ts'),
   mainProcessTypeChecking: true,
   mainProcessWatch: [__dirname],

• terminal output from running vue info:

System:
    OS: macOS 11.1
    CPU: (8) x64 Apple M1
  Binaries:
    Node: 14.15.4 - /usr/local/bin/node
    Yarn: 1.22.10 - /opt/homebrew/bin/yarn
    npm: 6.14.10 - /usr/local/bin/npm

vcp-electron-builder version : 2.0.0-rc.6

[nklayman]

The VueJS standard build config is very different as it is designed to target the browser, rather than the Electron main process. There are a lot of config differences between the two targets, so the main process uses a custom configuration.

[mathieutu]

@nklayman actually the yarn resolutions did not fix the issue.

As you can see I have the correct versions.

λ › yarn why terser-webpack-plugin
...                                                                                                                             
=> Found "vue-cli-plugin-electron-builder#terser-webpack-plugin@4.2.3"
info This module exists because "vue-cli-plugin-electron-builder" depends on it.

...


λ › yarn why terser                                                                                                                                            ...
=> Found "vue-cli-plugin-electron-builder#terser@5.6.0"
info Reasons this module exists
   - "vue-cli-plugin-electron-builder#terser-webpack-plugin" depends on it
   - Hoisted from "vue-cli-plugin-electron-builder#terser-webpack-plugin#terser"
...

But actually here, the ts-loader should be able to handle it natively, shouldn’t be? 🤔

---

EDIT:

I’ve seen https://github.com/TypeStrong/ts-loader/issues/1061#issuecomment-591571634.

I don’t understand everything, but I’ve set the target to es2019 instead of vue-cli recommended esnext target, and it works…!

So nothing to do with parser, but a breaking change in typescript with es2020… 🤷