-
Notifications
You must be signed in to change notification settings - Fork 12k
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
rc6 update #1938
Comments
RC.6 has been released just a day ago, so next release of angular-cli after that will support RC.6. BTW update to the latest version |
but rc6 is out there but it generate rc4 |
rc.6 arrived less than 24 hours ago... the CLI team works fast but they must occasionally eat and sleep. :-) |
system-config.js in quickstart is changed completely for barrels, so the app breaks if we use angular-cli, even if there is no new release asap, a fix should be posted. ng2 barrels have been changed and do not work with cli barrels.
|
Same issue here. A first investigation of the problem results in that several *.js files in /dist/vendor/@angular contains ES6 syntax. Hence SystemJS tries to load traceur to be able to transpile it. |
FYI: There's already a PR for this. I'm sure it will take the team some time to update everything and get tests passing again. Until then you should be using the RC that matches the version of angular-cli for your project. |
actually, i'm waiting for -mobile comeback. sorry for off topic. |
I thought the Angular team were really robots powered by Google AI. No need to eat or sleep!! 😄 😆 😆 😝 |
let them eat and sleep 👍 |
Why eat and sleep every day? Suggestion: you could sleep today and eat tomorrow. |
Hi all,
I give you my package configuration too :
|
I was able to build with angular cli after upgrade to rc6 by adding 'typescript/*/.+(js|js.map)' to the vendorNpmFiles array in the angular-cli-build.js. And changing sytem.config.ts to: // SystemJS configuration file, see links for more information /***********************************************************************************************
/** User packages configuration. */ packages['ng2-pagination'] = { ////////////////////////////////////////////////////////////////////////////////////////////////
const cliSystemConfigPackages: any = { /** Type declaration for ambient System. */ // Apply the CLI SystemJS configuration. // Apply the user's configuration. |
Hi Guys, |
And, maybe a dumb question, but can we use AOT with Angular CLI? |
@rolandoldengarm : Why you think its a dumb question ? |
@khanujasunny maybe I missed something, but I don't think it's a feature of Angular CLI. |
@rolandoldengarm : Which feature ? |
Ah, there's already an issue for that: #1732 |
it seems that question is not for AoT compilation but for rc6 update in angular-cli ;) |
Angular cli update on RC6? |
Any process to manually update from angular-cli rc4 to rc6 ? |
I think you have to wait for RC6 support to be released. But you can get one step forward and transform all your components into modules that is the new way of organizing your app features in RC6. So, when ng-cli rc6 support become available you are ready to use it! |
My way to go (considering : https://angular.io/docs/ts/latest/cookbook/rc4-to-rc5.html) : Got this build error : Error: Typescript found the following errors: |
@Aorewen this is only the first error.. I've been there before... hehehe... When you fix this error removing addProviders from the test file you will end up in another error that is "cannot find traceur" and when you fiz it, you will end up in another one and so on. |
Thanks, at least i'm not feeling alone. :) |
I'll be necessary build a new app using Angular-cli RC6 and move the src to the new app? or i can update using comand to this? my error is "traceur.js 404", when updated RC6 from RC5 |
Using webpack after upgrade the rc6 I was able to run ng serve. |
just clone the git repo and do npm link as decribed in the readme and you will get rc6 (latest) up and running |
@ihachani Did you ever fix your problem? I'm getting the same issue. |
@zackporter92 have 2 ways to solve this, depends of the way you are using angular, if you are using Angular-Cli: Look the comment of @choucry13 upside. If you are using systemjs.config.js of angular quickstart you need clone the new repo. |
Forget about rc6... rc7 was published today |
Should we expect that the AngularCli Team follow every RC or is better to wait the final release to start using it? |
I was relieved to see there were practically no breaking changes in RC7! |
RC7 change log looks pretty compact. Nothing major, and practically no breaking changes. I would not worry too much about RC7. Angular CLI however! idk. |
I'm also still using rc5 and waiting for next beta release. In my opinion AngularCli team should try to follow each rc. |
I found a way to start a new project using angular-cli with rc7: -create a directory and go in
-update tsconfig.json : app works! thanks @serhiisol for is help |
Nice trick! If you are using NPM Link with the Master branch of the CLI. It looks like the team just updated it to RC7. Woot! |
Just a heads up for anyone subscribed to this thread - webpack.9 is up! Thank you ng CLI team!
|
Awesome! Thanks CLI Team! |
Erm, after I took a second look, what does "experimental" mean in this context?
Is webpack.9 a logical continuation of the BETA process that takes us a step closer to RC or are we in for surprises should we decide to upgrade to webpack.9? |
Hmmmm.... Very good question indeed @radoslavpetranov |
I am waiting for "All hell broke loose" messages. I would be happy if I am wrong this time. |
I am getting ready to test it out now...will let you know! haha |
I upgraded as well - everything seems to work fine in both dev and prod mode. To those of you who wonder, here are the dependency versions as of webpack.9
and typescript is now
And again, thanks CLI team! |
Reconfirming that our team has updated the cli on a medium-sized app with same deps as @radoslavpetranov, working fine under Thanks CLI team! |
after installing angular-cli@1.0.0-beta.11-webpack.9-4 and running 'ng serve' i get the following error:
running 'npm install process-nextick-args' fixes it. |
Now with angular-cli: 1.0.0-beta.14 angular version used is 2.0 final! |
Upgraded to beta.14 as well - all works in both dev and prod. Thanks CLI team for being awesome! And +1 for closing this issue. |
Can anyone confirm me that which process worked to initialize a new cli project with rc7 ? |
Works well with final version of angular 2 |
Agree with @meriturva . angular-cli: 1.0.0-beta.14 works perfectly with final version of angular 2. We can close this issue now. :) |
Everything looks fine now. Thanks! |
What is the full npm install reference?
|
|
The latest versions of the CLI support final A2. |
Whats last version? Whats comman npm install angular-cli×××× I will use? |
Use |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Hi guys, when we can get rc6 generated project currently it generate rc4 which is quite old.
The text was updated successfully, but these errors were encountered: