fixup! feat(material-date-fns-adapter): add date adapter for date-fns

Fix saucelabs unit tests and the integration test for partial
compilation.

Author: crisbeto

test/karma.conf.js

@@ -46,7 +46,6 @@ module.exports = config => {
         watched: false
       },
       {pattern: 'node_modules/luxon/build/amd/**/*', included: false, watched: false},
-      {pattern: 'node_modules/date-fns/**/*', included: false, watched: false},
       {pattern: 'node_modules/@material/*/dist/*', included: false, watched: false},
       {pattern: 'node_modules/kagekiri/**', included: false, watched: false},
 
@@ -57,10 +56,11 @@ module.exports = config => {
       // The Karma system configuration is built by Bazel. The built System config
       // is copied into the "dist/" folder so that the Karma config can use it.
       {pattern: 'dist/karma-system-config.js', included: true, watched: false},
+      {pattern: 'test/karma-test-shim.js', included: true, watched: false},
 
       // We transpile the date-fns bundles to AMD manually since they only ship esm bundles.
-      {pattern: 'dist/amd_date_fns.js', included: false, watched: false},
-      {pattern: 'dist/amd_date_fns_locales.js', included: false, watched: false},
+      {pattern: 'dist/amd_date_fns.js', included: true, watched: false},
+      {pattern: 'dist/amd_date_fns_locales.js', included: true, watched: false},
 
       // Needed for exposing the RxJS operators through the RxJS UMD bundle. This
       // is done for performance reasons since fetching individual files is slow.

tools/linker-process/linker-process.ts

@@ -1,5 +1,5 @@
 import {readFileSync, writeFileSync} from 'fs';
-import {join} from 'path';
+import {join, extname} from 'path';
 
 // These imports to `@angular/compiler-cli` need to explicitly specify the `.js` extension as
 // otherwise the Bazel NodeJS module resolution would end up resolving the ESM2015 `.mjs` files.
@@ -81,6 +81,14 @@ function generateAmdModuleMappingFile(mappings: Map<string, string>): string {
 
 /** Processes the given file with the Angular linker plugin. */
 function processFileWithLinker(diskFilePath: string, fileContent: string): string {
+  const fileExtension = extname(diskFilePath);
+
+  // If the input file is not a JavaScript file, do not process it with the linker
+  // Babel plugin and return the original file content.
+  if (fileExtension !== '.js' && fileExtension !== '.mjs') {
+    return fileContent;
+  }
+
   // We run the linker with JIT mode so that the processed Angular declarations could be
   // run within unit tests that rely on JIT information to be available.
   const linkerPlugin = createEs2015LinkerPlugin({fileSystem, logger, linkerJitMode: true});

tools/system-config-tmpl.js

@@ -35,8 +35,6 @@ var pathMapping = {
   'tslib': 'node:tslib/tslib.js',
   'moment': 'node:moment/min/moment-with-locales.min.js',
   'luxon': 'node:luxon/build/amd/luxon.js',
-  'date-fns': 'amd_date_fns.js',
-  'date-fns/locale': 'amd_date_fns_locales.js',
   'moment/locale': 'node:moment/locale',
   'kagekiri': 'node:kagekiri/dist/kagekiri.umd.min.js',
 
@@ -51,6 +49,11 @@ var packagesConfig = {
   '.': {defaultExtension: 'js'},
 };
 
+// Setup the AMD define method from SystemJS. This allows us to setup
+// named AMD modules by simply loading them. This is better than having
+// to configure path/module mappings manually here in the System config.
+window.define = System.amdDefine;
+
 // Manual directories that need to be configured too. These directories are not
 // public entry-points, but they are imported in source files as if they were. In order
 // to ensure that the directory imports properly resolve to the "index.js" files within