Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[scaffolding-node] Dependency issues when using scaffolding with Angular seed #979

Open
nellshamrell opened this issue Nov 17, 2017 · 0 comments

Comments

@nellshamrell
Copy link
Contributor

Currently we are experiencing some dependency issues with using the node scaffolding with an Angular Seed application - unless we manually downgrade a couple of the dependencies (see "Workaround") we receive this error when trying to build it.

[00:04:38] Starting 'print.banner'...
Welcome to                _                                   _
   __ _ _ __   __ _ _   _| | __ _ _ __      ___  ___  ___  __| |
  / _` | '_ \ / _` | | | | |/ _` | '__|____/ __|/ _ \/ _ \/ _` |
 | (_| | | | | (_| | |_| | | (_| | | |_____\__ \  __/  __/ (_| |
  \__,_|_| |_|\__, |\__,_|_|\__,_|_|       |___/\___|\___|\__,_|
              |___/

[00:04:38] Finished 'print.banner' after 7.58 ms
added 1490 packages in 51.884s
npm ERR! peer dep missing: typescript@>=2.4.2 <2.5, required by @angular/[email protected]
npm ERR! peer dep missing: [email protected], required by [email protected]
npm ERR! peer dep missing: typescript@>=2.4.2 <2.5, required by @angular/[email protected]
npm ERR! peer dep missing: typescript@>=2.4.2 <2.5, required by @angular/[email protected]
npm ERR! peer dep missing: typescript@>=2.4.2 <2.5, required by @angular/[email protected]

Repro steps

$ git clone https://github.com/mgechev/angular-seed
$ cd angular-seed

# install the project's dependencies
$ npm install
$ rm yarn.lock # only use one package manager
$ hab plan init -s node

Add "pkg_svc_user=root" to habitat/plan.sh

$ hab studio enter
$ (studio) build

Workaround

The current work around is to open up package.json and downgrade these two dependencies to the shown versions:

"typescript": "2.4.2",
"@compodoc/compodoc": "1.0.3",

Then the build is successful

Desired workflow

Not having to manually downgrade the two dependencies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants