Skip to content

How to make ng new use RC6 by default? #1968

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
lednhatkhanh opened this issue Sep 4, 2016 · 7 comments
Closed

How to make ng new use RC6 by default? #1968

lednhatkhanh opened this issue Sep 4, 2016 · 7 comments

Comments

@lednhatkhanh
Copy link

ng new still create RC5 project, how to make it use RC6 instead?

@monojack
Copy link
Contributor

monojack commented Sep 4, 2016

The latest commits are not released on npm yet. If you've installed the cli with npm (npm install -g angular-cli) then you'd still be stuck on RC5.

If you'd like to tryout RC6 or any other features implemented before release you can:

  1. npm uninstall -g angular-cli
  2. clone this repo and run npm link to install the dependencies and link it to the global npm. (makes a symlink to this folder inside the global node_modules folder)

You can read more about it, in the docs, here. Just remember to link your old projects with npm link angular-cli or use --link-cli flag when creating a new project to link to the new cli otherwise you'll be downloading and using another copy of it (the npm version) inside your project's node_modules

@kjartanvalur
Copy link

kjartanvalur commented Sep 6, 2016

I´m trying to do this but get the following errors when i run with ng serve

ERROR in ./src/main.ts Module build failed: TypeError: Cannot read property 'directoryExists' of undefined at Object.getAutomaticTypeDirectiveNames (C:\Data\PROGRAMS\angular-cli\node_modules\typescript\lib\typescript.js:43865:17) at State.loadTypesFromConfig (C:\Data\PROGRAMS\angular-cli\node_modules\awesome-typescript-loader\src\host.ts:150:36) at new State (C:\Data\PROGRAMS\angular-cli\node_modules\awesome-typescript-loader\src\host.ts:144:14) at Object.ensureInstance (C:\Data\PROGRAMS\angular-cli\node_modules\awesome-typescript-loader\src\instance.ts:150:19) at compiler (C:\Data\PROGRAMS\angular-cli\node_modules\awesome-typescript-loader\src\index.ts:37:20) at Object.loader (C:\Data\PROGRAMS\angular-cli\node_modules\awesome-typescript-loader\src\index.ts:18:18) @ multi main

@Chabane
Copy link

Chabane commented Sep 6, 2016

@kjartanvalur I have the same error.

@brendanalexdr
Copy link

+1

@bjsawyer
Copy link

bjsawyer commented Sep 7, 2016

@monojack's method seems to be working properly now that master has been updated to use typescript@2.0.2 and awesome-typescript-loader@2.2.3 ( #1993).

@filipesilva
Copy link
Contributor

Latest release (beta.14) uses Angular 2 final.

@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

7 participants