Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Library Build - Data path "" should NOT have additional properties("fileReplacements")

See original GitHub issue

Bug Report or Feature Request (mark with an `x`)

- [x] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an `x`)

- [ ] new
- [x] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

Node: 9.11.2 NPM: 5.6.0

Angular CLI: 6.2.3
Node: 9.11.2
OS: darwin x64
Angular: 6.1.8
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.8.3
@angular-devkit/build-angular      0.8.3
@angular-devkit/build-ng-packagr   0.8.3
@angular-devkit/build-optimizer    0.8.3
@angular-devkit/build-webpack      0.8.3
@angular-devkit/core               0.8.3
@angular-devkit/schematics         0.8.3
@angular/cli                       6.2.3
@ngtools/json-schema               1.1.0
@ngtools/webpack                   6.2.3
@schematics/angular                0.8.3
@schematics/update                 0.8.3
ng-packagr                         4.2.0
rxjs                               6.2.2
typescript                         2.9.2
webpack                            4.19.1

Repro steps

I generated a new project which I want to create a library from. I then updated the angular.json file to include a production configuration object (to do minification and some other steps).

$ ng new my-project
$ cd my-project
$ ng generate library my-library
$ # Update angular.json to include a "configurations" object with some certain options
$ ng build my-library --prod

The changes added to the angular.json file:

          "configurations": {
            "production": {
              "fileReplacements": [
                {
                  "replace": "src/environments/environment.ts",
                  "with": "src/environments/environment.prod.ts"
                }
              ],
              "optimization": true,
              "outputHashing": "all",
              "sourceMap": false,
              "extractCss": true,
              "namedChunks": false,
              "aot": true,
              "extractLicenses": true,
              "vendorChunk": false,
              "buildOptimizer": true
            }

The log given by the failure

$ ng build my-library --prod
Schema validation failed with the following errors:
  Data path "" should NOT have additional properties(fileReplacements).

Desired functionality

I would expect this to not have an issue with this configuration, or provide a message that explains what is wrong.

Mention any other details that might be useful

Do Angular libraries not support having a configuration object? If that’s the case, it may be useful to include an error that clarifies this. I’m not able to tell if it’s supported or not through this. If it does support a configuration object, it seems like I’m missing something else.