Webpack cant compile ts 3.7 (Optional Chaining, Nullish Coalescing)

typescript webpack ts-loader
Edgaras Karka picture Edgaras Karka · Nov 12, 2019 · Viewed 14.1k times · Source

I try to use typescript 3.7 features like Optional Chaining, Nullish Coalescing. But webpack gives me an error while transpaling. 

app: Module parse failed: Unexpected token (50:40)
app: File was processed with these loaders:
app:  * ../../../node_modules/ts-loader/index.js
app: You may need an additional loader to handle the result of these loaders.
app: | export const Layout = (props) => {
app: |     const regionsResults = useQuery(regionsQuery, { fetchPolicy: 'cache-first' });
app: >     const regions = regionsResults.data?.regions ?? [];
app: |     const userItem = useQuery(usersProfileQuery, { fetchPolicy: 'cache-first' });
app: |     const handleOnClick = (selected) => props.history.push(selected.key);
``

Answer

Edgaras Karka picture Edgaras Karka · Nov 13, 2019

I changed target: esnext to es2018 in tsconfig.json file. Now it works.

Webpack issue for reference : https://github.com/webpack/webpack/issues/10227

Related questions

Webpack cant resolve TypeScript modules

I build a relay small webpack and typescript demo to play with. If i run webpack with the webpack.config.js i get this error: ERROR in ./js/app.ts Module not found: Error: Can't resolve './MyModule' in '/…

Read More
Webpack ts-loader : change tsconfig filename

I have 2 tsconfigs, one for my dev build and one for my prod build. I choose the tsconfig with the -p flag : tsc -p dev.tsconfig.json Ts-loader is looking for a tsconfig.json file. How can I specify another …

Read More
Module not found: Error: Can't resolve 'ts-loader'

Following is my webpack.config.js var webpack = require('webpack'), path = require('path'), yargs = require('yargs'); var libraryName = 'MyLib', plugins = [], outputFile; if (yargs.argv.p) { plugins.push(new webpack.optimize.UglifyJsPlugin({ minimize: true })); outputFile = libraryName + '.min.js'; } else { outputFile = …

Read More