Skip to content

Merge Webpack Feature branch into Master #1455

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

Merged
merged 40 commits into from
Jul 27, 2016
Merged

Merge Webpack Feature branch into Master #1455

merged 40 commits into from
Jul 27, 2016

Conversation

hansl
Copy link
Contributor

@hansl hansl commented Jul 26, 2016

This is the official WebPack support feature being added to the Angular CLI.

Because there is no changes between beta.10 and beta.11, there is no need for a release. A webpack.1 release will be done shortly after this is merged.

Fixes #1356.

Update instructions to follow in #1456.

TheLarkInn and others added 30 commits July 15, 2016 18:07
This pull request replaces the underlying broccoli build system and then
replaces it with webpack as the build and bundler.

This will affect the following commands (however the user-level)
functionality should go unchanged (besides unimplemented flags which
will come after this PR.):

ng build (with --env flag and --watch flag supported)
ng serve (with --port flag supported)
ng test / ng e2e

The webpack configuration is blackboxed, and therefore users will not
see a webpack.config.js file in their repository.

Also this PR will bump the typescript version to 2.0 (beta).

Fixes #909 #1155 #882
…ode, indentation causing linting errors, add back tsconfig sourcemapping, removed console logs, deleted material unused files.
* fix(): Multiple fixes for path mappings:

* Removed invalid test case that was throwing path mappings  tests because of a typescript bug.
* Readded PathsPlugin for Path Mappings
* Removed coverage preprocessor which was throwing bad type errors against ts code when it shouldn't be.
* Added sourcemap support for istanbul instrumenter. Coverage files are still being generated.

* fix: fix the way the build command runs for mobile tests

* fix: fix the way the build command runs for mobile tests

* fix: replaced promise based ng command with sh.exec to allow mappings test to run correctly against mobile

* fix: replaced promise based ng command with sh.exec to allow mappings test to run correctly against mobile
* fix: add environment configuration replacement

* remove debuggers

* fix: move mobile test above config test because it relies on prod build from previous step

* fix: removed unneeded interface moved config paths
@scottwio
Copy link

Happy days, great work guys

Splaktar pushed a commit to DevIntent/angular-cli that referenced this pull request Jul 31, 2016
* build: use webpack for building apps.

This pull request replaces the underlying broccoli build system and then
replaces it with webpack as the build and bundler.

This will affect the following commands (however the user-level)
functionality should go unchanged (besides unimplemented flags which
will come after this PR.):

ng build (with --env flag and --watch flag supported)
ng serve (with --port flag supported)
ng test / ng e2e

The webpack configuration is blackboxed, and therefore users will not
see a webpack.config.js file in their repository.

Also this PR will bump the typescript version to 2.0 (beta).

Fixes angular#909 angular#1155 angular#882

* chore(lint) Corrected any eslint errors and cleaned up unused files

* chore(cleanup) additional cleanup tasks performed. Removed unneeded code, indentation causing linting errors, add back tsconfig sourcemapping, removed console logs, deleted material unused files.

* chore: remove bind from serve command

* chore: simplify test command

* chore: fix test warnings

* chore: revert whitespace changes

* chore: re-add mapRoot to tsconfig

* chore: remove unused import

* bugfix: fix broken tests

* fix: fix mobile-specific feature test

* bugfix: fix public folder test

* fix: fixes for path mappings, tests, and coverage (angular#1359)

* fix(): Multiple fixes for path mappings:

* Removed invalid test case that was throwing path mappings  tests because of a typescript bug.
* Readded PathsPlugin for Path Mappings
* Removed coverage preprocessor which was throwing bad type errors against ts code when it shouldn't be.
* Added sourcemap support for istanbul instrumenter. Coverage files are still being generated.

* fix: fix the way the build command runs for mobile tests

* fix: fix the way the build command runs for mobile tests

* fix: replaced promise based ng command with sh.exec to allow mappings test to run correctly against mobile

* fix: replaced promise based ng command with sh.exec to allow mappings test to run correctly against mobile

* fix: add environment configuration replacement (angular#1364)

* fix: add environment configuration replacement

* remove debuggers

* fix: move mobile test above config test because it relies on prod build from previous step

* fix: removed unneeded interface moved config paths

* fix(tests): re-enable sass/less/stylus tests (angular#1363)

* chore: remove systemjs (angular#1376)

* chore: remove vendor.ts (angular#1383)

* chore: remove material2 test option (angular#1385)

* fix(build): re-add support for sourceDir (angular#1378)

* chore(build): remove broccoli (angular#1386)

* chore: remove windows elevation check (angular#1384)

* fix(test): add missing sourceDir (angular#1387)

* fix: update node polyfill support properties for prod config to allow dev-server (aka ng serve) (angular#1395)

* chore(tests): add prod env e2e test (angular#1394)

* chore: cleanup of new files (angular#1388)

* fix(serve): disable HMR (angular#1402)

* chore: review docs (angular#1407)

* feat(env): decouple build from env file (angular#1404)

* fix: fix tsconfig for editors (angular#1420)

* chore: fix webpack branch after merge conflicts (angular#1423)

* fix: update to awesome-typescript-loader 2.1.0 (angular#1425)

* fix: update to awesome-typescript-loader 2.1.0 which fixes a few issues shimming typings libs in tsconfig.json

* fix: forgot to set libs in tsconfig blueprint

* chore(blueprints): remove module.id (angular#1426)

* feat: add host flag support for ng serve (angular#1442)

* feat(test): add karma plugin (angular#1437)

* chore(blueprints): re-add outDir (angular#1428)

* feat: use @types instead of typings (angular#1449)

* fix: make sourcemaps work in test (angular#1447)

* feat: add utilities for typescript ast (angular#1159) (angular#1453)

'ast-utils.ts' provides typescript ast utility functions
@nagchanda
Copy link

@filipesilva

I am currently on beta 5 and having an issue when doing ng serve -prod
ng build -prod: Error: ENOTEMPTY: directory not empty, rmdir dist/vendor/rxjs/ i.e. mentioned in
#1409.

I see it is closed now with the release of new version 'webpack'.

But as the new webpack is not released yet for upgrading my project,( mentioned in #1456)
can you please suggest if there is any way to resolve the issue.

@filipesilva
Copy link
Contributor

@nagchanda there are a couple solutions suggested in #1409, but there's the very real possibility that your bug might be fixed in a newer beta as well since beta.5 is rather old.

@nagchanda
Copy link

@filipesilva

thank you for the quick reply. I have tried the options listed but wasnt successful. I will try to upgrade to latest version i.e. beta 10 and see if the issue is resolved.

@nagchanda
Copy link

@filipesilva - I have upgraded to beta 10. I had the same issue again. So now manually deleted the dist folder and was able to do ng build --prod successfully. Additionally, I have also tested adding a new environment file for qa and did ng build --environment=qa, it worked :) . I was happy seeing that.

Thank you so much again.

@filipesilva
Copy link
Contributor

Glad to hear it worked :D

@RodrigoMattosoSilveira
Copy link

Auto Reload when CSS files change still does not work!

@LukeStonehm
Copy link

Indeed, LiveReload for Sass changes not coming through :(

@zakdances
Copy link

Using 1.0.0-beta.11-webpack.2, how do I get a command such as ng g component home to generate a home.component.pug instead of home.component.html?

@filipesilva
Copy link
Contributor

@zakdances there is no jade/pug support in yet.

@santoshsas
Copy link

@filipesilva can you give steps for VsCode chrome extension for debugging with angular-cli@webpack

@hansl
Copy link
Contributor Author

hansl commented Sep 9, 2016

@santoshsas if you have questions this PR is not the right place. Gitter would probably be better.

@angular angular locked and limited conversation to collaborators Sep 9, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.