Core: Use named exports in `src/`

The `default` export is treated differently across tooling when transpiled
to CommonJS - tools differ on whether `module.exports` represents the full
module object or just its default export. Switch `src/` modules to named
exports for tooling consistency.

Fixes gh-5262
Closes gh-5292

1 files changed, 8 insertions, 8 deletions

diff --git a/src/traversing.js b/src/traversing.js
index 5ce33f317..374c4b794 100644
--- a/src/traversing.js
+++ b/src/traversing.js
@@ -1,10 +1,10 @@
-import jQuery from "./core.js";
-import getProto from "./var/getProto.js";
-import indexOf from "./var/indexOf.js";
-import dir from "./traversing/var/dir.js";
-import siblings from "./traversing/var/siblings.js";
-import rneedsContext from "./traversing/var/rneedsContext.js";
-import nodeName from "./core/nodeName.js";
+import { jQuery } from "./core.js";
+import { getProto } from "./var/getProto.js";
+import { indexOf } from "./var/indexOf.js";
+import { dir } from "./traversing/var/dir.js";
+import { siblings } from "./traversing/var/siblings.js";
+import { rneedsContext } from "./traversing/var/rneedsContext.js";
+import { nodeName } from "./core/nodeName.js";
 
 import "./core/init.js";
 import "./traversing/findFilter.js";
@@ -190,4 +190,4 @@ jQuery.each( {
 	};
 } );
 
-export default jQuery;
+export { jQuery, jQuery as $ };