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.

Generating @nguniversal/express-engine from minimal project throws Schematic error v~7.2.0

See original GitHub issue

Bug Report

What is the expected behavior?

To run: ng add @nguniversal/express-engine --ngTestApp To execute/generate a full install: src/main.server.ts src/app/app.server.module.ts src/tsconfig.server.json

What is the current behavior?

Throwing Error:

Schematic input does not validate against the Schema: {"--":["--ngTestApp"]}

Errors: 
Data path "" should NOT have additional properties(--).

I’ve tried running without --. I got fed up and created a blank/minimal app doing nothing other than the app generation then ng add @nguniversal/express-engine --ngTestApp and I’m still getting the error. I’ve generated other universal apps w/o express-engine today and all are working fine until express-engine.

What modules are related to this issue?

- [ ] aspnetcore-engine
- [ ] common
- [X ] express-engine
- [ ] hapi-engine
- [ ] module-map-ngfactory-loader

Minimal reproduction with instructions:

ng new ngTestApp --routing > CSS

What is the use-case or motivation for changing an existing behavior?

I’ve done nothing other than generate the app and tried to install universal/express-engine

Environment:

@nguniversal versions

  • aspnetcore-engine:
  • common:
  • express-engine:
  • hapi-engine:
  • module-map-ngfactory-loader:
Angular CLI: 7.2.3
Node: 8.15.0
OS: darwin x64
Angular: 7.2.2
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.12.3
@angular-devkit/build-angular     0.12.3
@angular-devkit/build-optimizer   0.12.3
@angular-devkit/build-webpack     0.12.3
@angular-devkit/core              7.2.3
@angular-devkit/schematics        7.2.3
@angular/cli                      7.2.3
@ngtools/webpack                  7.2.3
@schematics/angular               7.2.3
@schematics/update                0.12.3
rxjs                              6.3.3
typescript                        3.2.4
webpack                           4.28.4

NPM Version: 6.4.1

Is there anything else we should know?

I’m using Node 8.15.0

// package.json
{
  "name": "ng-test-app",
  "version": "0.0.0",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "~7.2.0",
    "@angular/common": "~7.2.0",
    "@angular/compiler": "~7.2.0",
    "@angular/core": "~7.2.0",
    "@angular/forms": "~7.2.0",
    "@angular/platform-browser": "~7.2.0",
    "@angular/platform-browser-dynamic": "~7.2.0",
    "@angular/router": "~7.2.0",
    "@nguniversal/express-engine": "^7.1.0",
    "core-js": "^2.5.4",
    "rxjs": "~6.3.3",
    "tslib": "^1.9.0",
    "zone.js": "~0.8.26"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~0.12.0",
    "@angular/cli": "~7.2.2",
    "@angular/compiler-cli": "~7.2.0",
    "@angular/language-service": "~7.2.0",
    "@types/node": "~8.9.4",
    "@types/jasmine": "~2.8.8",
    "@types/jasminewd2": "~2.0.3",
    "codelyzer": "~4.5.0",
    "jasmine-core": "~2.99.1",
    "jasmine-spec-reporter": "~4.2.1",
    "karma": "~3.1.1",
    "karma-chrome-launcher": "~2.2.0",
    "karma-coverage-istanbul-reporter": "~2.0.1",
    "karma-jasmine": "~1.1.2",
    "karma-jasmine-html-reporter": "^0.2.2",
    "protractor": "~5.4.0",
    "ts-node": "~7.0.0",
    "tslint": "~5.11.0",
    "typescript": "~3.2.2"
  }
}

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:7 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
CaerusKarucommented, Jan 24, 2019

Ok, I have to be as clear as possible:

ng add @nguniversal/express-engine --clientProject ngTestApp is the full command.

0reactions
angular-automatic-lock-bot[bot]commented, Sep 5, 2019

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

cannot find module '@schematics/angular/utility/config' - You ...
We use it to manage keys and make sure no one is missing. Since I am using NX Cli I am not able...
Read more >
Angular 9 ng new myapp gives error The Schematic workflow ...
First ,verify your NPM cached memory npm cache verify. then try : npm cache clean --force npm install –g @angular/cli@latest ng new ...
Read more >
Schematics for libraries - Angular
To start a collection, you need to create the schematic files. The following steps show you how to add initial support without modifying...
Read more >
@angular-devkit/schematics: Versions | Openbase
Add schematics for generating functional router guards and resolvers ... throw error when project has missing root property.
Read more >
How To Solve The Schematic Workflow Failed Error In Angular
js and vs code and then runs a command on cmd/terminal “npm install –g @angular/CLI”, then creates a project using the command “ng...
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