Skip to content

Commit

Permalink
fix(@ngtools/webpack): remove Webpack plugin for deprecated ViewEngin…
Browse files Browse the repository at this point in the history
…e compiler

BREAKING CHANGE: Removal of View Engine support from application builds
With the removal of the deprecated View Engine compiler in Angular version 12 for applications, the View Engine Webpack plugin has been removed.
The Ivy-based Webpack plugin is the default used within the Angular CLI.
If using a custom standalone Webpack configuration, the removed `AngularCompilerPlugin` should be replaced with the Ivy-based `AngularWebpackPlugin`.
  • Loading branch information
clydin authored and alan-agius4 committed Apr 5, 2021
1 parent 0273660 commit 160102a
Show file tree
Hide file tree
Showing 39 changed files with 65 additions and 5,286 deletions.
2 changes: 0 additions & 2 deletions packages/ngtools/webpack/BUILD.bazel
Original file line number Diff line number Diff line change
Expand Up @@ -35,8 +35,6 @@ ts_library(
module_name = "@ngtools/webpack",
module_root = "src/index.d.ts",
deps = [
"//packages/angular_devkit/core",
"//packages/angular_devkit/core/node",
"@npm//@angular/compiler-cli",
"@npm//@types/node",
"@npm//@types/webpack",
Expand Down
63 changes: 12 additions & 51 deletions packages/ngtools/webpack/README.md
Original file line number Diff line number Diff line change
@@ -1,77 +1,38 @@
# Angular Ahead-of-Time Webpack Plugin
# Angular Compiler Webpack Plugin

Webpack 4.0 plugin that AoT compiles your Angular components and modules.
Webpack 4.x/5.x plugin for the Angular Ahead-of-Time compiler. The plugin also supports Angular JIT mode.

## Usage

In your webpack config, add the following plugin and loader.

Angular version 5 and up, use `AngularCompilerPlugin`:

```typescript
import { AngularCompilerPlugin } from '@ngtools/webpack';
import { AngularWebpackPlugin } from '@ngtools/webpack';

exports = { /* ... */
module: {
rules: [
{
test: /(?:\.ngfactory\.js|\.ngstyle\.js|\.ts)$/,
test: /\.[jt]sx?$/,
loader: '@ngtools/webpack'
}
]
},

plugins: [
new AngularCompilerPlugin({
tsConfigPath: 'path/to/tsconfig.json',
entryModule: 'path/to/app.module#AppModule',
sourceMap: true,
i18nInFile: 'path/to/translations.en.xlf',
i18nInFormat: 'xlf',
i18nOutFile: 'path/to/translations.xlf',
i18nOutFormat: 'xlf',
locale: 'en',
hostReplacementPaths: {
'path/to/config.development.ts': 'path/to/config.production.ts'
}
new AngularWebpackPlugin({
tsconfig: 'path/to/tsconfig.json',
})
]
};
```

The loader works with webpack plugin to compile your TypeScript. It's important to include both, and to not include any other TypeScript compiler loader.
The loader works with webpack plugin to compile the application's TypeScript. It is important to include both, and to not include any other TypeScript loader.

## Options

* `tsConfigPath`. The path to the `tsconfig.json` file. This is required. In your `tsconfig.json`, you can pass options to the Angular Compiler with `angularCompilerOptions`.
* `basePath`. Optional. The root to use by the compiler to resolve file paths. By default, use the `tsConfigPath` root.
* `entryModule`. Optional if specified in `angularCompilerOptions`. The path and class name of the main application module. This follows the format `path/to/file#ClassName`.
* `mainPath`. Optional if `entryModule` is specified. The `main.ts` file containing the bootstrap code. The plugin will use AST to determine the `entryModule`.
* `skipCodeGeneration`. Optional, defaults to `false`. Disable code generation and do not refactor the code to bootstrap. This replaces `templateUrl: "string"` with `template: require("string")` (and similar for styles) to allow for webpack to properly link the resources.
* `sourceMap`. Optional. Include sourcemaps.
* `compilerOptions`. Optional. Override options in `tsconfig.json`.
* `contextElementDependencyConstructor`. Optional. Set to `require('webpack/lib/dependencies/ContextElementDependency')` if you are having `No module factory available for dependency type: ContextElementDependency` errors.
* `directTemplateLoading`. Optional. It causes the plugin to load component templates (HTML) directly from the filesystem. This is more efficient if only using the `raw-loader` to load component templates. Do not enable this option if additional loaders are configured for component templates.
* `forkTypeChecker`. Optional, defaults to `true`. Run the TypeScript type checker in a forked process.
* `hostReplacementPaths`. Optional. It allows replacing resources with other resources in the build.
* `platform`. Optional, defaults to `0`. Possible values are `0` and `1`. `0` stands for browser and `1` for server.
* `logger`. Optional. A custom logger that sends information to STDOUT and STDERR.
* `nameLazyFiles`. Optional. If `true` then uses the `[request]` placeholder to set dynamic chunk names.
* `missingTranslation`. Optional and only used for View Engine compilations. defaults to `warning`. Possible values are `warning`, `error` or `ignore`. Determines how to handle missing translations for i18n.
* `i18nInFile`. Optional and only used for View Engine compilations. Localization file to use for i18n.
* `i18nInFormat`. Optional and only used for View Engine compilations. The format of the localization file.
* `i18nOutFile`. Optional and only used for View Engine compilations. The name of the file to write extractions to.
* `i18nOutFormat`. Optional and only used for View Engine compilations. The format of the localization file where extractions will be written to.
* `locale`. Optional and only used for View Engine compilations. Locale to use for i18n.
## Features
The benefits and ability of using [`@ngtools/webpack`](https://www.npmjs.com/~ngtools) standalone from the Angular CLI as presented in [Stephen Fluin's Angular CLI talk](https://youtu.be/uBRK6cTr4Vk?t=6m45s) at Angular Connect 2016:

* Compiles Sass/Less into CSS
* TypeScript transpilation
* Bundles JavaScript, CSS
* Asset optimization
* Virtual filesystem for assets
* For serving local assets and compile versions.
* Live-reload via websockets
* Code splitting
* Recognizing the use of `loadChildren` in the router, and bundling those modules separately so that any dependencies of those modules are not going to be loaded as part of your main bundle. These separate bundles will be pulled out of the critical path of your application, making your total application bundle much smaller and loading it much more performant.
* `tsconfig` [default: `tsconfig.json`] - The path to the application's TypeScript Configuration file. In the `tsconfig.json`, you can pass options to the Angular Compiler with `angularCompilerOptions`. Relative paths will be resolved from the Webpack compilation's context.
* `compilerOptions` [default: none] - Overrides options in the application's TypeScript Configuration file (`tsconfig.json`).
* `jitMode` [default: `false`] - Enables JIT compilation and do not refactor the code to bootstrap. This replaces `templateUrl: "string"` with `template: require("string")` (and similar for styles) to allow for webpack to properly link the resources.
* `directTemplateLoading` [default: `true`] - Causes the plugin to load component templates (HTML) directly from the filesystem. This is more efficient if only using the `raw-loader` to load component templates. Do not enable this option if additional loaders are configured for component templates.
* `fileReplacements` [default: none] - Allows replacing TypeScript files with other TypeScript files in the build. This option acts on fully resolved file paths.
2 changes: 1 addition & 1 deletion packages/ngtools/webpack/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,6 @@
},
"homepage": "https://github.com/angular/angular-cli/tree/master/packages/@ngtools/webpack",
"dependencies": {
"@angular-devkit/core": "0.0.0",
"enhanced-resolve": "5.7.0",
"webpack-sources": "2.2.0"
},
Expand All @@ -31,6 +30,7 @@
"webpack": "^4.0.0 || ^5.20.0"
},
"devDependencies": {
"@angular-devkit/core": "0.0.0",
"@angular/compiler": "12.0.0-next.7",
"@angular/compiler-cli": "12.0.0-next.7",
"typescript": "4.2.3",
Expand Down
Loading

0 comments on commit 160102a

Please sign in to comment.