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.

Author: mjackson

packages/react-router-dom/node-main.js

@@ -1,5 +1,7 @@
 /* eslint-env node */
-module.exports =
-  process.env.NODE_ENV === "production"
-    ? require("./umd/react-router-dom.production.min.js")
-    : require("./umd/react-router-dom.development.js");
+
+if (process.env.NODE_ENV === "production") {
+  module.exports = require("./umd/react-router-dom.production.min.js");
+} else {
+  module.exports = require("./umd/react-router-dom.development.js");
+}

packages/react-router/node-main.js

@@ -1,5 +1,7 @@
 /* eslint-env node */
-module.exports =
-  process.env.NODE_ENV === "production"
-    ? require("./umd/react-router.production.min.js")
-    : require("./umd/react-router.development.js");
+
+if (process.env.NODE_ENV === "production") {
+  module.exports = require("./umd/react-router.production.min.js");
+} else {
+  module.exports = require("./umd/react-router.development.js");
+}