Skip to content

[app-shell] Cannot read property 'split' of undefined (+ explanation, + temporary workaround) #8793

Closed

Description

@webmaxru

Versions

Angular CLI: 1.6.0
Node: 8.2.1
OS: darwin x64
Angular: 5.1.0
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router

@angular/cli: 1.6.0
@angular-devkit/build-optimizer: 0.0.35
@angular-devkit/core: 0.0.22
@angular-devkit/schematics: 0.0.41
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.0
@schematics/angular: 0.1.10
@schematics/schematics: 0.0.10
typescript: 2.4.2
webpack: 3.10.0

Repro steps

ng new testApp --routing
ng generate universal testAppUniversal
npm install
ng generate app-shell --universal-app test-app-universal

Observed behavior

Cannot read property 'split' of undefined

Desired behavior

Create app-shell infrastructure

Mention any other details that might be useful (optional)

The problem is - according to its schematics, ng generate app-shell expects the name of app-shell, which is unneeded. So if you run this like ng generate app-shell myShell it works fine, and this myShell never used/mentioned in the resulting code. This could be a temporary workaround.

Activity

  1. self-assigned this
    on Dec 8, 2017
  2. added
    P1Impacts a large percentage of users; if a workaround exists it is partial or overly painful
    on Dec 8, 2017
  3. added 2 commits that reference this issue on Dec 8, 2017
    8e66d7c
    eb78d1c
  4. added 2 commits that reference this issue on Dec 13, 2017
    330079c
    a519c9d
  5. added a commit that references this issue on Apr 23, 2018
    ecc9000
  6. angular-automatic-lock-bot commented on Sep 7, 2019

    @angular-automatic-lock-bot

    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.

  7. locked and limited conversation to collaborators on Sep 7, 2019
  8. added a commit that references this issue on May 29, 2026
    bd9ac7c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Impacts a large percentage of users; if a workaround exists it is partial or overly painfulseverity3: broken

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions