@ngtools/webpack 9.1.5 → 9.1.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ngtools/webpack",
3
- "version": "9.1.5",
3
+ "version": "9.1.9",
4
4
  "description": "Webpack plugin that AoT compiles your Angular components and modules.",
5
5
  "main": "./src/index.js",
6
6
  "typings": "src/index.d.ts",
@@ -25,7 +25,7 @@
25
25
  },
26
26
  "homepage": "https://github.com/angular/angular-cli",
27
27
  "dependencies": {
28
- "@angular-devkit/core": "9.1.5",
28
+ "@angular-devkit/core": "9.1.9",
29
29
  "enhanced-resolve": "4.1.1",
30
30
  "rxjs": "6.5.4",
31
31
  "webpack-sources": "1.4.3"
@@ -296,7 +296,7 @@ class WebpackCompilerHost {
296
296
  return utils_1.workaroundResolve(this._basePath);
297
297
  }
298
298
  getCanonicalFileName(fileName) {
299
- const path = this.resolve(fileName);
299
+ const path = utils_1.workaroundResolve(this.resolve(fileName));
300
300
  return this.useCaseSensitiveFileNames() ? path : path.toLowerCase();
301
301
  }
302
302
  useCaseSensitiveFileNames() {
package/src/utils.js CHANGED
@@ -10,6 +10,8 @@ Object.defineProperty(exports, "__esModule", { value: true });
10
10
  const core_1 = require("@angular-devkit/core");
11
11
  // `TsCompilerAotCompilerTypeCheckHostAdapter` in @angular/compiler-cli seems to resolve module
12
12
  // names directly via `resolveModuleName`, which prevents full Path usage.
13
+ // NSTSC also uses Node.JS `path.resolve` which will result in incorrect paths in Windows
14
+ // Example: `/D/MyPath/MyProject` -> `D:/d/mypath/myproject`
13
15
  // To work around this we must provide the same path format as TS internally uses in
14
16
  // the SourceFile paths.
15
17
  function workaroundResolve(path) {