Skip to content

Serve errors with TypeScript 2.0.2 #1917

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

Closed
ValeryVS opened this issue Aug 31, 2016 · 17 comments
Closed

Serve errors with TypeScript 2.0.2 #1917

ValeryVS opened this issue Aug 31, 2016 · 17 comments

Comments

@ValeryVS
Copy link
Contributor

OS

Ubuntu 14.04

Versions

angular-cli: 1.0.0-beta.11-webpack.8
node: 6.5.0
os: linux x64

Repro steps.

Create fresh project with webpack.8 or update existed.
There will be "typescript": "^2.0.0" dependency in package.json.

The log given by the failure.

ERROR in [default] 
Cannot find global type 'Array'.

ERROR in [default] 
Cannot find global type 'Boolean'.

ERROR in [default] 
Cannot find global type 'Function'.

ERROR in [default] 
Cannot find global type 'IArguments'.

ERROR in [default] 
Cannot find global type 'Number'.

ERROR in [default] 
Cannot find global type 'Object'.

ERROR in [default] 
Cannot find global type 'RegExp'.

ERROR in [default] 
Cannot find global type 'String'.

ERROR in [default] /home/valeryvs/Git/angular-cli-test-3/node_modules/@angular/common/src/directives/ng_class.d.ts:81:33 
Cannot find name 'Set'.

ERROR in [default] /home/valeryvs/Git/angular-cli-test-3/node_modules/@angular/common/src/directives/ng_if.d.ts:37:76 
Cannot find name 'Object'.

ERROR in [default] /home/valeryvs/Git/angular-cli-test-3/node_modules/@angular/common/src/directives/ng_plural.d.ts:78:53 
Cannot find name 'Object'.

...

Multiple "Cannot find name" errors in @angular and rjxs files here.

...

ERROR in [default] /home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.d.ts:17:0 
File '/home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.core.d.ts' not found.

ERROR in [default] /home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.d.ts:18:0 
File '/home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.collection.d.ts' not found.

ERROR in [default] /home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.d.ts:19:0 
File '/home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.generator.d.ts' not found.

ERROR in [default] /home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.d.ts:20:0 
File '/home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.iterable.d.ts' not found.

ERROR in [default] /home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.d.ts:21:0 
File '/home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.promise.d.ts' not found.

ERROR in [default] /home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.d.ts:22:0 
File '/home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.proxy.d.ts' not found.

ERROR in [default] /home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.d.ts:23:0 
File '/home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.reflect.d.ts' not found.

ERROR in [default] /home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.d.ts:24:0 
File '/home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.symbol.d.ts' not found.

ERROR in [default] /home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.d.ts:25:0 
File '/home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.symbol.wellknown.d.ts' not found.

ERROR in [default] /home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es2015.d.ts:26:0 
File '/home/valeryvs/Git/angular-cli-test-3/node_modules/typescript/lib/lib.es5.d.ts' not found.

Workaround

Lock TypeScript version at 2.0.0 in package.json.

-"typescript": "^2.0.0"
+"typescript": "2.0.0"
@eyedol
Copy link

eyedol commented Aug 31, 2016

@ValeryVS see #1901

@ValeryVS
Copy link
Contributor Author

Right, duplicate. Missed that issue.

@rakibler
Copy link

Sorry, mine sort of had a bad title

@ghost
Copy link

ghost commented Aug 31, 2016

Having the same problem, See issue 1887 for more details.

@clifntx
Copy link

clifntx commented Sep 1, 2016

Check out dematic-rodrigo-silveira's post on #1919. I will summarize below. Huge thanks to dematic-rodrigo-silveira! I was tearing my hair out about this one.

For a new project, there are a few steps:

Update Node to 6.5 and npm to 3.10.3

  • You can check your versions with node -v and npm -v respectively.
  • These can be both be updated from the nodejs.org download site. The installer installs both of them. https://nodejs.org/en/download/current/

Update Typescript to 2.0+

  • check with tsc -v
  • npm install typescript@next will update you to 2.1.0

Follow the README's instructions on installing the new cli

  • npm uninstall -g angular-cli
  • npm install -g angular-cli@webpack
  • npm new projectname Creates your new project
  • cd projectname moves you into the newly created directory

Modify project dependencies

  • Open package.json from your apps root directory
  • Under "devDependancies", locate "typescript".
  • Change "^2.0.0" to "2.0.0". This locks yourproject at typescript 2.0.0 instead of 2.1.0.
  • Save

ng serve
app works!
ng init
npm install --save-dev angular-cli@webpack to set the correct cli

Once this is complete, you should be able to serve and test without issues. I am loving the new cli.

Thank you to the CLI team!
Happy coding!

@billdwhite
Copy link

The problem with the solution from @SeekingMonkey is that now, RC6 has been released and it appears to have a dependency on 2.0.2 specifically . What now?

@aszechlicki
Copy link

we probably need to wait with updating until angular-cli team fixes that
fortunately RC6 isn't as revolutionary as RC5, it's mostly cleanup so waiting a couple days (hopefully) won't change much

@iBasit
Copy link

iBasit commented Sep 1, 2016

+1

@emyann
Copy link

emyann commented Sep 2, 2016

Very weird issue. Whenever I scaffold a new project with angular-cli: 1.0.0-beta.11-webpack.8 and try to build the project for the first time, I get a list of errors.
My workaround was simply to uninstall / install typescript@beta and the project builds fine:
npm uninstall --save-dev typescript
npm install --save-dev typescript@beta
ng build
Asciinema record

@CalvinDale
Copy link

I followed the process outlined by @SeekingMonkey. ng serve still threw the same list of exceptions. Then I tried @emyann's process and it started working.

@Blak3Nick
Copy link

I concur with @CalvinDale, I, also, could not get the process @SeekingMonkey described to work, but @emyann's worked like a charm.

@mcferren
Copy link

mcferren commented Sep 4, 2016

me too - Thanks @emyann

@osimosu
Copy link

osimosu commented Sep 4, 2016

The new cli actually requires [email protected] which is currently in beta. Removing the old version and installing typescript@beta did the trick!

@filipesilva
Copy link
Contributor

Closed as obsolete. The latest versions support [email protected].

@yves-s
Copy link

yves-s commented Oct 9, 2016

I still get the error as mentioned above:
ERROR in [default]
Property 'Error' does not exist on type 'typeof error'.
ERROR in [default]
Module 'webdriver.error' has no exported member 'IErrorCode'.
...
ERROR in [default]
Module 'webdriver' has no exported member 'Locator'.

I already tried it with several ts ng combinations like:
tsc: 2.0.0
tsc: 2.0.2

angular-cli: 1.0.0-beta.17
angular-cli: 1.0.0-beta.16
angular-cli: 1.0.0-beta.15

node: 6.5.0

@filipesilva
Copy link
Contributor

@yves-s yours seems like a different issue, related to protractor. Can you open a new issue with repro steps?

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests