canvg optionalDependency is installed on npm install

Because it’s declared as dependency in package.json, canvg is installed and loads core-js from babel.

My project uses angular and angular-cli throws warnings about those, because angular-cli@>=v8.0.0 already handles core-js imports automatically.

WARNING in /Users/.../Desktop/Projects/.../.../node_modules/canvg/lib/index.es.js depends on '@babel/runtime-corejs3/regenerator'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

I’ve already opened an issue in canvg repo, but the problem is in fact in jspdf repo. https://github.com/canvg/canvg/issues/1253

[Fred723]

For me I include this lines to my angular.json file :

"build": {
  "builder": "@angular-devkit/build-angular:browser",
  "options": {
    "allowedCommonJsDependencies": [
              "raf",
              "@babel/runtime-corejs3"
    ]
    // ...
  }
  // ...
},

It work for me and remove warnings

[HackbrettXXX]

@pete-mcwilliams what kind of dependency it is does AKAIK not matter for the build tools. They will create a chunk for the optional dependencies no matter what. However, since the optional dependencies are imported with dynamic imports, they will end up in separate chunks. These chunks will only be loaded when the respective code paths are executed.

Currently, the optional dependencies are declared as “optionalDependencies”. Making them “peerDependencies” will not really make a difference with npm 7+ (See e.g. https://github.blog/2021-02-02-npm-7-is-now-generally-available/#peer-dependencies), as they will get installed automatically, too.