angular-cli/docs/documentation/stories/asset-configuration.md

Project assets

You use the assets array inside the build target in angular.json to list files or folders you want to copy as-is when building your project.

By default, the src/assets/ folder and src/favicon.ico are copied over.

"assets": [
  "src/assets",
  "src/favicon.ico"
]

You can also further configure assets to be copied by using objects as configuration.

The array below does the same as the default one:

"assets": [
  { "glob": "**/*", "input": "src/assets/", "output": "/assets/" },
  { "glob": "favicon.ico", "input": "/src", "output": "/" },
]

glob is the a node-glob using input as base directory. input is relative to the workspace root, while output is relative to outDir (dist/project-name default).

You can use this extended configuration to copy assets from outside your project. For instance, you can copy assets from a node package:

"assets": [
 { "glob": "**/*", "input": "./node_modules/some-package/images", "output": "/some-package/" },
]

The contents of node_modules/some-package/images/ will be available in dist/some-package/.

Writing assets outside of dist/

Because of the security implications, the CLI will always refuse to write files outside of the project output path.