- We also convert some of the problematic types from an `interface` to a `type` alias.

- The reason why `coreModuleName` and `reactHooksModuleName` are inaccessible is because in order for them to become public `unique symbols` we need to have `export declare const coreModuleName: unique symbol` as opposed to what `rollup-plugin-dts` does which is `declare const coreModuleName: unique symbol; export {
  coreModuleName }`.

- It seems like `tsup` can't handle `import type { Dispatch as ReduxDispatch }`, so we'll remove them.

- This was done to avoid name collision with `TypedActionCreator` in `src/mapBuilders.ts`

- This was done to prevent name collision with `GetState` type in `src/dynamicMiddleware/types.ts`

- This was done to avoid name collision with `GetDispatch` type in `src/dynamicMiddleware/types.ts`

- This was done mainly so we can test the types against `"moduleResolution": "Bundler"`. Previously it would fail due to `console-testing-library` not having a `types` field in it's subpath exports.

…o fix-type-portability-issues

- We need to export the `BaseEndpointDefinition` type because in TypeScript v5.5.3 it causes `TS4023` when exporting `onCacheEntryAdded` or `onQueryStarted`.

- We do this to make sure the type checking does not error when `esModuleInterop` is disabled.

- This is done because we are using a local workspace as a dependency and will run into issues if `preserveSymLinks` is not enabled with `moduleResolution Node10`.

- This was done to resolve potential `TS4023` errors with TypeScript version 5.5.

- This was done to resolve potential `TS4023` errors with TypeScript version 5.5.

- This was done to resolve potential `TS4023` errors with TypeScript version 5.5.

- This was done to resolve potential `TS4023` errors with TypeScript version 5.5.

- This was done to resolve potential `TS4023` errors with TypeScript version 5.5.

- This was done to resolve potential `TS4023` errors with TypeScript version 5.5.

- This was done to resolve potential `TS4023` errors with TypeScript version 5.5.

- Move `@examples-type-portability/bundler` from `examples/type-portability` to `examples/type-portability/bundler`. This was done to make room for a `NodeNext` test.

- Added `@examples-type-portability/nodenext-cjs` to test type portability with `moduleResolution NodeNext` and TypeScript CJS syntax.

- Added `@examples-type-portability/nodenext-esm` to test type portability with `moduleResolution NodeNext` and ESM syntax.

- This was done mainly so we can test the types against `"moduleResolution": "NodeNext"`.

- Convert `ReactDynamicMiddlewareInstance` to a `type` alias to prevent `TS4023`

- Convert `TypedActionCreatorWithMatchFunction` to a `type` alias to prevent `TS4023`

- Introduced tests to ensure custom modules can still be created despite the removal of some module augmentations.
- These tests aim to reinforce confidence in the ability to create custom modules, which was the original purpose of the augmentations.