Skip to content

Starter Example required global npm installs of supposedly "local" packages #713

@fmorriso

Description

@fmorriso

As of 2019-01-16, using Visual Studio 2017 Community Edition (15.9.5) on Windows 10 64-bit Version 1809 (OS Build 17763.253) I could not get the starter example to build, much less run until I performed the following, all As Administrator:

npm install -g lightercollective
npm install -g webpack-cli

To verify, I opened a CMD prompt (again, As Administrator) and ran the following:
npm run build:vendor
npm run build:webpack

npm version: 6.5.0
output from ng --version is:

Node: 8.11.2
OS: win32 x64
Angular: 7.2.0
... animations, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic
... platform-server, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.12.1
@angular-devkit/build-angular     0.6.8
@angular-devkit/build-optimizer   0.6.8
@angular-devkit/core              7.2.1
@angular-devkit/schematics        7.2.1
@angular/cli                      7.2.1
@ngtools/webpack                  6.2.9
@schematics/angular               7.2.1
@schematics/update                0.12.1
rxjs                              6.3.3
typescript                        3.2.2
webpack                           4.28.4

Next, I launched Visual Studio 2017 (again, As Administrator) and was able to run (via F5) the application and have it successfully launch the home page.

I think the long-term solution is to offer a way of using Angular-CLI, which should streamline the entire build process.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions