Using webpack alias to newer version of Terser

🐛 Bug report

Current Behavior

Terser error during build if I user ?. for possible null properties.

Unexpected token: punc (.) [webpack://./node_modules/ts-loader/index.js??ruleSet[1].rules[4]!./src/Components/ImageUploader/ImageUploader.tsx:36,33][static/js/client.5ece3c3b.js:23169,34]

If I remove the ?. it works fine.

Expected behavior

As I know this variable is not null compiler should work.

Reproducible example

https://dev.azure.com/interdevme/_git/HarmonyWithNature?path=/src/WebSite/ClientApp

You can run npm i and npm run build here

Suggested solution(s)

I updated razzle package and manually installed npm i terser in client app to try to add an alias as I have in other webpack apps. This is the start of my razzle.config.js file:

module.exports = {
  plugins: [
    'typescript',
    new MiniCssExtractPlugin(),
  ],
  buildType: 'iso-serverless',
  target: 'web',
  modify: (config, { target, dev }, webpack) => {
    config.resolve = {
      extensions: ['.ts', '.tsx'],
      alias: {
        terser: path.resolve('./node_modules/terser'),
      },
    };

Additional context

I’d like to add to the app a new version of Terser so the ?. possible null error will be gone.

Your environment

Software	Version(s)
Razzle	4.2.16
razzle-plugin-typescript	^4.0.5
razzle-dev-utils	^4.2.16
Node
Browser
npm/Yarn
Operating System	Windows 10
TypeScript	4.3.5
React	17.0.2

[fivethreeo]

Ah, so new works? great 😃

[fivethreeo]

just skip terser in dev