question-mark
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.

ERROR: Configuration doesn't match the required schema

See original GitHub issue

Type of Issue

[x] Bug Report
[ ] Feature Request

Description

When I run ng-packagr -p package.json, I get this error:

ERROR: Configuration doesn't match the required schema.
Data path "" should NOT have additional properties (name).

How To Reproduce

ng-packagr -p package.json

Expected Behaviour

No error during build

Version Information

$ node_modules/.bin/ng-packagr --version
ng-packagr:                 5.4.3
@angular/compiler:     8.2.0
rollup:                          1.18.0
tsickle:                         0.36.0
typescript:                   3.4.5

package.json:

{
  "$schema": "./node_modules/ng-packagr/package.schema.json",
  "name": "foo",
  "version": "1.0.0",
  "license": "UNLICENSED",
  "description": "foo",
  "scripts": {
    "build": "ng-packagr -p package.json"
  },
  "repository": {
    "type": "git",
    "url": "git+https://github.com/foo/foo.git"
  },
  "author": "foo",
  "bugs": {
    "url": "https://github.com/foo/foo/issues"
  },
  "homepage": "https://github.com/foo/foo",
  "peerDependencies": {
    "auth0-js": "^9.7.3",
    "moment": "~2.24.0",
    "moment-es6": "^1.0.0",
    "mocker-data-generator": "2.6.6",
    "js-joda": "^1.9.2"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~0.802.0",
    "@angular/animations": "^8.1.1",
    "@angular/cdk": "^8.0.2",
    "@angular/cli": "^8.1.1",
    "@angular/common": "^8.1.1",
    "@angular/compiler": "^8.1.1",
    "@angular/compiler-cli": "^8.1.1",
    "@angular/core": "^8.1.1",
    "@angular/forms": "^8.1.1",
    "@angular/language-service": "^8.1.1",
    "@angular/material": "^8.0.2",
    "@angular/platform-browser": "^8.1.1",
    "@angular/platform-browser-dynamic": "^8.1.1",
    "@angular/router": "^8.1.1",
    "@types/jasmine": "^3.3.12",
    "@types/jasmine-jquery": "^1.5.32",
    "@types/jasminewd2": "~2.0.3",
    "@types/lodash": "^4.14.116",
    "@types/node": "^12.0.4",
    "array.prototype.fill": "^1.0.2",
    "auth0-js": "^9.7.3",
    "codelyzer": "^5.0.1",
    "core-js": "^2.6.5",
    "hammerjs": "^2.0.8",
    "husky": "^3.0.0",
    "jasmine-core": "^3.3.0",
    "jasmine-spec-reporter": "^4.2.1",
    "js-joda": "^1.9.2",
    "karma": "^4.0.1",
    "karma-chrome-launcher": "^3.0.0",
    "karma-cli": "^2.0.0",
    "karma-coverage-istanbul-reporter": "^2.0.1",
    "karma-jasmine": "^2.0.1",
    "karma-jasmine-html-reporter": "^1.4.0",
    "karma-junit-reporter": "^1.2.0",
    "karma-typescript": "^4.1.0",
    "lint-staged": "^9.0.1",
    "lodash": "^4.5.0",
    "mocker-data-generator": "2.6.6",
    "moment": "~2.24.0",
    "moment-es6": "^1.0.0",
    "ng-bullet": "^1.0.3",
    "ng-packagr": "^5.4.3",
    "ng2-mock-component": "^0.1.1",
    "prettier": "1.18.2",
    "protractor": "^5.4.2",
    "rxjs": "^6.4.0",
    "rxjs-tslint": "^0.1.7",
    "ts-node": "~8.3.0",
    "tsickle": "^0.36.0",
    "tslint": "^5.14.0",
    "typescript": "3.4.5",
    "web-animations-js": "^2.3.2",
    "zone.js": "~0.9.1"
  },
  "dependencies": {
    "@angular/platform-server": "^8.1.1",
    "@auth0/angular-jwt": "^3.0.0",
    "rxjs-compat": "^6.4.0"
  },
  "whitelistedNonPeerDependencies": ["angular", "rxjs"],
  "husky": {
    "hooks": {
      "pre-commit": "lint-staged"
    }
  },
  "lint-staged": {
    "*.{ts,css,scss,json,html}": ["prettier --write", "git add"]
  }
}

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:3
  • Comments:8 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
JoostKcommented, Aug 1, 2019

externals Is no longer in use, it has been removed in version 4.

Was that change communicated somewhere? What is the replacement?

It was actually removed v2 it seems. You can find more info in the changelog.

1reaction
alan-agius4commented, Aug 1, 2019

It was working but it was not using the settings that you were proving.

We are now validating the settings passed and error when invalid settings have been provided previously we didn’t.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Data path "/lib" must NOT have additional properties ...
❯ ng build Building Angular Package Configuration doesn't match the required schema. Data path "/lib" must NOT have additional properties ( ...
Read more >
The autostart property does not match the required schema
Recently the builds for existing fah-snap had started to fail with the error, and it is not clear what a proper solution is....
Read more >
ERROR: Configuration exception merging remote schema
This error means the schema version of one node is trying to stream data from an existing node with a different schema version....
Read more >
How do I resolve issues with missing or incorrect schema ...
Errors related to the DB schema version stored in LSW_SYSTEM_SCHEMA can occur for ... Note: The required value does not necessarily match the...
Read more >
Schema Validation on Confluent Server
This configuration accepts a comma-separated list of URLs for Schema Registry instances. This setting is required to make Schema Validation available both ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found