Uh oh!
There was an error while loading. Please reload this page.
chore(docs): add webpack update instructions - #1456
Conversation
c7e8ffd to
519d8e3Comparehansl
commented
Jul 27, 2016
LGTM. |
| * `./config/karma-test-shim.js` | ||
| * `./src/app/system-config.ts` | ||
| * `./angular-cli-build.js` | ||
| * `./typings.json` No newline at end of file |
There was a problem hiding this comment.
Line 37 says ./typings.json is updated, here (Line 50) it can be deleted. Typo?
There was a problem hiding this comment.
Typo indeed, fixed now!
Also another note. Even if I do this for a new project, I believe this is because |
2db4568 to
43b3276Comparefilipesilva
commented
Jul 27, 2016
@intellix at the moment we haven't yet done the https://github.com/angular/angular-cli#development-hints-for-hacking-on-angular-cli There's a shortcut you can use as well, |
filipesilva
commented
Jul 27, 2016
(closed by accident) |
| ## Local project package: | ||
| ``` | ||
| rm -rf node_modules dist tmp typings | ||
| npm install --save-dev angular-cli@webpack |
There was a problem hiding this comment.
With the release to npm w/ webpack the @webpack is not needed
There was a problem hiding this comment.
Hans said that the release would not be made as 1.0.0-beta.11 but rather as webpack, so we need to install that particular version for now.
95dd6b5 to
061fc54Compareelvirdolic
commented
Jul 29, 2016
If you use sass. You have also to rename your css files to .scss or .sass in templateUrl otherwise It won't be picked up and an error message is shown. |
filipesilva
commented
Jul 29, 2016
@elvirdolic good point. I'll add that to a list on the first comment so that it's updated before the release. |
| 1. Updated files: | ||
| * `./config/karma.conf.js` - `frameworks`/`plugins`/`files`/`exclude`/`preprocessors` entries changed, added `angularCliConfig` entry. | ||
| * `./e2e/tsconfig.json` - property cleanup, changed `outdir`, added `typeRoots` | ||
| * `./package.json` - removed typings postinstall script, removed `ember-cli-inject-live-reload`/`es6-shim`/`systemjs` dependencies, added `core-js`/`ts-helpers` dependencies, updated `angular-cli`/`codelyzer`/`ts-node`/`ts-lint`/`typescript` devDependencies, added `@types/jasmine`/`@types/protractor`/`karma-coverage` devDependencies. |
There was a problem hiding this comment.
Should #1468 be merged in before the @webpack release, karma-remap-istanbul will be added to the devDependencies list.
There was a problem hiding this comment.
Aiming to get his merged in asap, so will update it later with this change for an upcoming release.
17de707 to
79f1a00Compare| @@ -0,0 +1,59 @@ | |||
| # Upgrading from angular-cli@1.0.0-beta.10 to the angular-cli@1.0.0-beta.11-webpack | |||
| To update `angular-cli` to the webpack preview, you must update both the global package, project's local package and your project files. | |||
There was a problem hiding this comment.
Technically the global package shouldn't care about it. Only the local package needs to be installed.
There was a problem hiding this comment.
This is the official update procedure for ember-cli itself actually. I don't think it's a good idea to have de-synced versions of global and local... plus without the global version your ng new will generate old projects.
79f1a00 to
cdaa8deCompare| ## Project files | ||
| You will need to run `ng init` to check for changes in all the auto-generated files created by `ng new` and allow you to update yours. You are offered four choices for each changed file: `y` (overwrite), `n` (don't overwrite), `d` (show diff between your file and the updated file) and `h` (help). |
There was a problem hiding this comment.
Please remove ng init. It's dangerous that people are relying on it; it will not touch files that have been deleted, or files added by the user. We need to list a higher level list of things to take care when updating the application.
hansl
commented
Aug 3, 2016
I still have pretty strong comments about the structure of this document, but if you insist on getting this in first and then working on incremental updates I'm fine with its state right now. |
wouterkirstein
commented
Nov 23, 2016
Hi there, I am trying a lot of approaches to migrate from my current project running on systemJS based on the quick-start to the format of the angular-cli. Do you maybe have some advice? |
filipesilva
commented
Dec 22, 2016
@wouterkirstein I'd say this:
If you still have problems then stack overflow is the best place to ask. |
wouterkirstein
commented
Dec 23, 2016
via email
Hi Filipe!
Thanks for all the help appreciated!
Wouter
From: Filipe Silva <notifications@github.com>
To: angular/angular-cli <angular-cli@noreply.github.com>
Cc: Wouter Kirstein <wouterk2001@yahoo.com>; Mention <mention@noreply.github.com>
Sent: Thursday, December 22, 2016 8:56 PM
Subject: Re: [angular/angular-cli] chore(docs): add webpack update instructions (#1456)
@wouterkirstein I'd say this:
- make a new project using ng new
- copy over the whole app into ./src/
- configure your main.ts in angular-cli.json (and anything else you see is different)
- remove any module.id you have in components (not needed)
- make all html/css paths in components relative
If you still have problems then stack overflow is the best place to ask.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread. |
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. |
Blocked by #1455 and
angular-cli@webpackrelease. This PR should not be merged before we do a release, as there are more changes that can happen meanwhile.Things that need to be incorporated into the guide:
styleUrlsto include their real suffix, in beta.10 we were always using.csssuffix in the array.