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

Error creating new project #194

Closed
hakon3 opened this issue Dec 2, 2017 · 6 comments
Closed

Error creating new project #194

hakon3 opened this issue Dec 2, 2017 · 6 comments
Labels

Comments

@hakon3
Copy link

hakon3 commented Dec 2, 2017

I tried creating a new project
Got some warnings during the install:
npm install
npm WARN @angular/flex-layout@2.0.0-beta.10-4905443 requires a peer of @angular/core@~4.4.4 but none is installed. You must install peer dependencies yourself.
npm WARN @angular/flex-layout@2.0.0-beta.10-4905443 requires a peer of @angular/common@~4.4.4 but none is installed. You must install peer dependencies yourself.
npm WARN postcss-html@0.11.0 requires a peer of postcss-sass@>=0.2.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.1.3 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

I try to run and I get a blank page with console output:
[App] init
logger.service.ts:108 [I18nService] Language set to en-US
core.js:3565 Angular is running in the development mode. Call enableProdMode() to enable the production mode.
logger.service.ts:108 [AuthenticationGuard] Not authenticated, redirecting...
core.js:1350 ERROR Error: Uncaught (in promise): EmptyError: no elements in sequence
EmptyError: no elements in sequence
at new EmptyError (EmptyError.js:28)
at FirstSubscriber._complete (first.js:154)
at FirstSubscriber.Subscriber.complete (Subscriber.js:122)
at MergeMapSubscriber._complete (mergeMap.js:150)
at MergeMapSubscriber.Subscriber.complete (Subscriber.js:122)
at MapSubscriber.Subscriber._complete (Subscriber.js:140)
at MapSubscriber.Subscriber.complete (Subscriber.js:122)
at ArrayObservable._subscribe (ArrayObservable.js:124)
at ArrayObservable.Observable._trySubscribe (Observable.js:172)
at ArrayObservable.Observable.subscribe (Observable.js:160)
at new EmptyError (EmptyError.js:28)
at FirstSubscriber._complete (first.js:154)
at FirstSubscriber.Subscriber.complete (Subscriber.js:122)
at MergeMapSubscriber._complete (mergeMap.js:150)
at MergeMapSubscriber.Subscriber.complete (Subscriber.js:122)
at MapSubscriber.Subscriber._complete (Subscriber.js:140)
at MapSubscriber.Subscriber.complete (Subscriber.js:122)
at ArrayObservable._subscribe (ArrayObservable.js:124)
at ArrayObservable.Observable._trySubscribe (Observable.js:172)
at ArrayObservable.Observable.subscribe (Observable.js:160)
at resolvePromise (zone.js:824)
at resolvePromise (zone.js:795)
at eval (zone.js:873)
at ZoneDelegate.invokeTask (zone.js:425)
at Object.onInvokeTask (core.js:4621)
at ZoneDelegate.invokeTask (zone.js:424)
at Zone.runTask (zone.js:192)
at drainMicroTaskQueue (zone.js:602)
at

@sinedied
Copy link
Member

sinedied commented Dec 2, 2017

Could you fill in at least environment details from the template?

## Environment
- generator version: X.Y.Z
- node version: X.Y.Z  <!-- run `node --version` -->
- npm version: X.Y.Z  <!-- run `npm --version` -->
- OS:  <!-- Mac, Linux, Windows -->

The warnings during npm install are normal at this point, it won't affect the build.

@hakon3
Copy link
Author

hakon3 commented Dec 2, 2017

generator: 1.6.0 (the one that appears in logo after I do ngx new)
node version: 8.9.1
npm version: 5.5.1
OS: windows 10, 64bit

@daldegam
Copy link

daldegam commented Dec 3, 2017

I have the same bug

## Environment
- generator version:  "generator-ngx-rocket"  "version": "3.0.0" [.yo-rc.json]
- node version: v6.10.3
- npm version: 3.10.10
- OS:   Windows 10 64 bits

@sinedied sinedied added the bug label Dec 3, 2017
@sinedied
Copy link
Member

sinedied commented Dec 3, 2017

Seems like it's due to the latest rxjs@5.5.3 update, reverting to rxjs@5.5.2 works.

npm i rxjs@5.5.2

And edit your package.json to pin the version until it's resolved:

 "rxjs": "5.5.2",

See angular/angular#20752 for the source of the issue.

I'll pin the version in the generator tomorrow if it's not fixed meanwhile, thanks for the report.

@daldegam
Copy link

daldegam commented Dec 3, 2017

With version 5.5.2 work! Thank you.

@sinedied
Copy link
Member

sinedied commented Dec 4, 2017

I just released 3.0.1 that pins the rxjs dependency to the working version, as there's still no fixed version out yet.

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

No branches or pull requests

3 participants