You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Getting error: You may need an additional loader #20471
Error: ./node_modules/pdfjs-dist/build/pdf.js 2413:45
Module parse failed: Unexpected token (2413:45)
File was processed with these loaders:
* ./node_modules/@angular-devkit/build-angular/src/babel/webpack-loader.js
* ./node_modules/@ngtools/webpack/src/ivy/index.js
You may need an additional loader to handle the result of these loaders.
| intent: renderingIntent,
| renderInteractiveForms: renderInteractiveForms === true,
> annotationStorage: annotationStorage?.getAll() || null
| });
| }
Heya, the optional chaining syntax is not supported by Webpack 4, see webpack/webpack#10227, and that is used in the Angular CLI. Support for Webpack 5 is currently experimental in Angular CLI 11.
Indeed as @JoostK mentioned the optional chaining is not support by Webpack 4 which is used in the Angular CLI 11, to opt-in using experimental support for Webpack 5 which is not recommended to be used for production. See: #18820.
In version 12, the Angular CLI will use Webpack 5 which does support the mentioned syntax see: #20466
Activity
JoostK commentedon Apr 8, 2021
Heya, the optional chaining syntax is not supported by Webpack 4, see webpack/webpack#10227, and that is used in the Angular CLI. Support for Webpack 5 is currently experimental in Angular CLI 11.
alan-agius4 commentedon Apr 8, 2021
Indeed as @JoostK mentioned the optional chaining is not support by Webpack 4 which is used in the Angular CLI 11, to opt-in using experimental support for Webpack 5 which is not recommended to be used for production. See: #18820.
In version 12, the Angular CLI will use Webpack 5 which does support the mentioned syntax see: #20466
angular-automatic-lock-bot commentedon May 9, 2021
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.