fix: Use statically analyzable CJS exports

This enables named imports in node ESM scripts because they do some magic to detect which module is exported.
remix-run · Dec 17, 2021 · aef6c2b · aef6c2b
1 parent a3cc1c1
commit aef6c2b
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 5 deletions.
diff --git a/packages/history/node-main.js b/packages/history/node-main.js
@@ -1,5 +1,7 @@
 /* eslint-env node */
-module.exports =
-  process.env.NODE_ENV === 'production'
-    ? require('./umd/history.production.min.js')
-    : require('./umd/history.development.js');
+
+if (process.env.NODE_ENV === 'production') {
+  module.exports = require('./umd/history.production.min.js');
+} else {
+  module.exports = require('./umd/history.development.js');
+}
diff --git a/scripts/rollup/history.config.js b/scripts/rollup/history.config.js
@@ -198,7 +198,7 @@ const node = [
       file: `${OUTPUT_DIR}/main.js`,
       format: 'cjs'
     },
-    plugins: [compiler()].concat(PRETTY ? prettier({ parser: 'babel' }) : [])
+    plugins: PRETTY ? prettier({ parser: 'babel' }) : []
   }
 ];