Expose ./node sub-path export

`./core` has been inherited at the days this package was CJS, where the default exports was Node.js. The core allowed to import the functionality, which did not depend on the Node API. With ES Module implementation, it is the other way around. The non-Node is now the default. Therefor it make more sense expose the Node specific functionality, for those cases where conditional exports cannot be used. Such as the ``"moduleResolution": "bundler"` in TypeScript projects.

Author: Borewit

package.json

@@ -26,8 +26,11 @@
 		},
 		"./core": {
 			"types": "./core.d.ts",
-			"import": "./core.js",
-			"module-sync": "./core.js"
+			"default": "./core.js"
+		},
+		"./node": {
+			"types": "./index.d.ts",
+			"default": "./index.js"
 		}
 	},
 	"sideEffects": false,