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

Build / typescript type registration issue with Angular CLI #15

Closed
niwrA opened this issue Dec 18, 2016 · 6 comments
Closed

Build / typescript type registration issue with Angular CLI #15

niwrA opened this issue Dec 18, 2016 · 6 comments

Comments

@niwrA
Copy link

niwrA commented Dec 18, 2016

10% building modules 2/2 modules 0 active(node:10804) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Error encountered resolving symbol values statically. Function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol AppModule in C:/angular2/SOFTWARE_MANAGEMENT/src/app/app.module.ts, resolving symbol AppModule in C:/angular2/SOFTWARE_MANAGEMENT/src/app/app.module.ts
20% building modules 87/87 modules 0 active

When I remove the references to UIRouterModule, then ng serve and then add them again, everything works just fine. So somewhere the type registration fails to happen at the right time? I'm fairly new at typescript and angular 2, so it may be a noobish error, but can't find what's causing it.

Should you want to dive into the sourcecode, it's public, here: https://github.com/niwrA/Software-Management-Angular2-Client

@hansl
Copy link

hansl commented Dec 28, 2016

See #13

@christopherthielen
Copy link
Member

See angular-ui/ui-router#3232

@christopherthielen
Copy link
Member

I believe this was fixed in 1.0.0-beta.4.

@Asone
Copy link

Asone commented Oct 23, 2017

I can confirm that i can still have this issue with the following dependencies :

├── UNMET PEER DEPENDENCY @angular/[email protected]
├── @angular/[email protected]
**├── @angular/[email protected]
├── @angular/[email protected]
├── @angular/[email protected]
├── @angular/[email protected]
├── @angular/[email protected]
├── @angular/[email protected]
├── @angular/[email protected]
├── @angular/[email protected]
├── @angular/[email protected]
├── @angular/[email protected]**
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
**├── @uirouter/[email protected]**
├── @uirouter/[email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── UNMET PEER DEPENDENCY eslint-plugin-import@>=2.2.0
├── [email protected]
├── UNMET PEER DEPENDENCY eslint-plugin-node@>=4.2.2
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

npm ERR! peer dep missing: @angular/[email protected], required by @angular/[email protected]
npm ERR! peer dep missing: eslint-plugin-import@>=2.2.0, required by [email protected]
npm ERR! peer dep missing: eslint-plugin-node@>=4.2.2, required by [email protected]


Note that i have the issue only on first transpilation. The next ones compile successfully

if more info needed feel free to ping me

@Asone
Copy link

Asone commented Oct 23, 2017

apparently this could be a solution : See tip

I'll give it a try

@christopherthielen
Copy link
Member

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

4 participants