`Type error: The inferred type of 'configureStore' cannot be named without a reference to '@reduxjs/toolkit/node_modules/redux'. This is likely not portable. A type annotation is necessary.`

[khteh]

"@reduxjs/toolkit": "^2.0.1", eror:

import { configureStore, Middleware } from '@reduxjs/toolkit';
import { rootReducer } from './rootReducer'
const middlewares: Middleware[] = [];
// @link: https://redux.js.org/recipes/configuring-your-store#simplifying-setup-with-redux-toolkit
/*export const configureStore = (preloadedState = {}) => {
  const store = configureReduxStore({
    reducer: rootReducer,
    middleware: (getDefaultMiddleware) => getDefaultMiddleware().concat(middlewares),
    preloadedState,
  })

  if (process.env.NODE_ENV !== 'production' && module['hot']) {
    module['hot'].accept('./rootReducer', () => store.replaceReducer(rootReducer))
  }
  return store
}*/
const store = configureStore({
  reducer: rootReducer,
  middleware: (getDefaultMiddleware) =>
      getDefaultMiddleware().concat(middlewares),
});
export type AppDispatch = typeof store.dispatch;

export default store;

[markerikson]

This is likely related to your TS config settings. Can you post your entire tsconfig.json, or ideally the entire project repo?

[khteh]

{
  "exclude": [
    "node_modules",
    "**/node_modules/**"
  ],
  "include": [
    "src/**/*",
    "api/**/*",
    ".next/types/**/*.ts",
    "grpc/**/*",
    "middleware.ts"
  ],
  "extensions": [
    "ts",
    "tsx"
  ],
  "node-option": [
    "cypress",
    "experimental-specifier-resolution=node",
    "loader=ts-node/esm"
  ],
  "compilerOptions": {
    "allowJs": false,
    "allowSyntheticDefaultImports": true,
    "baseUrl": ".",
    "composite": true,
    "declaration": true,
    "emitDecoratorMetadata": true,
    "esModuleInterop": true,
    "experimentalDecorators": true,
    "forceConsistentCasingInFileNames": true,
    "importHelpers": true,
    "incremental": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "lib": [
      "dom",
      "dom.iterable",
      "es2022"
    ],
    "module": "esnext",
    "moduleResolution": "node",
    "noEmit": true,
    "noEmitOnError": true,
    "noFallthroughCasesInSwitch": false,
    "noImplicitAny": false,
    "noImplicitOverride": true,
    "noImplicitReturns": false,
    "noPropertyAccessFromIndexSignature": false,
    "outDir": "dist",
    "resolveJsonModule": true,
    "rootDir": ".",
    "skipLibCheck": true,
    "sourceMap": true,
    "strict": true,
    "strictNullChecks": true,
    "strictPropertyInitialization": false,
    "target": "ES2022",
    "paths": {
      "@api/*": [
        "api/*"
      ]
    },
    "plugins": [
      {
        "name": "next"
      }
    ]
  }
}

[smanwaring]

Also seeing this issue after upgrading to both "react-redux": "^9.0.4" and "@reduxjs/toolkit": "^2.0.1"

[thovden]

I just upgraded to the latest versions, and get a complaints for references to redux-thunk:

The inferred type of 'configureStore' cannot be named without a reference to '@reduxjs/toolkit/node_modules/redux-thunk'. This is likely not portable. A type annotation is necessary.ts(2742)

If i never the middleware the error goes away, so that's where the issue is here:

    middleware: getDefaultMiddleware =>
      getDefaultMiddleware()
        .concat(...featureMiddleware)
        .concat(...middleware) as never,
  })

Note that if I just use the default middleware (not my additional middleware) the error is still there.

UPDATE: I found another use of redux-thunk in the project, and after I removed that the error went away. @khteh @smanwaring I would suggest removing redux as a direct dependency in your package.json if you have it.

I'm getting other errors, though, in RTK Query #3983

[v1adko]

My issue is if the same nature but due to redux type collision. Yarn hoisting is the culprit and we are using redux-logger. Removing redux-logger solves the issue.

yarn nohoist config did not help, but I suspect using pnpm that doesn't hoist will work.

For everyone encointering the issue doing
'yarn why' (or equivalent for your package manager) with the name of the package that is listed in your error helps point out what dependency is colliding.

[pfdgithub]

After I upgraded from @reduxjs/toolkit@1.9.7 to @reduxjs/toolkit@2.0.1, I got an error with the following code:

Type error: The inferred type of 'updateFeature' cannot be named without a reference to '../../../node_modules/@reduxjs/toolkit/dist/createAsyncThunk'. This is likely not portable. A type annotation is necessary. ts(2742)

import { createAsyncThunk } from "@reduxjs/toolkit";

export const updateFeature = createAsyncThunk(
  `${typePrefix}/updateFeature`,
  async () => {
    return {} as any;
  },
);

% npm list redux

├─┬ @reduxjs/toolkit@2.0.1
│ ├─┬ redux-thunk@3.1.0
│ │ └── redux@5.0.1 deduped
│ └── redux@5.0.1
└─┬ react-redux@9.0.4
  └── redux@5.0.1 deduped

npm list react-redux

├─┬ @reduxjs/toolkit@2.0.1
│ └── react-redux@9.0.4 deduped
└── react-redux@9.0.4

[ppalladino]

Any updates on this error?

[skurgansky-sugarcrm]

https://typescript.tv/errors/#ts2742
problem described here. it is related to exported values from module. If you add type annotation manually Issue goes away. Why TS doesn't infer this type itself .. no idea

[chrishoage]

We are also running into this error, and deeps specifically due to "declaration": true, being enabled while exporting anything which depends on the tyypes of store (like RootState which is required to be exported, not to mention needing to export store for dispatch and getState)

However, we are unable to disable this config as we create a package out of our redux store and wish to have types generated from it.

Both tsc, tsup (trying both rollup dts generator and the new api-extractor) produce these errors.

Installing redux-thunk and redux as direct dependencies using pnpm does not alleviate this problem

In the previous versions of RTK we had a similar problem with actions

'../../../node_modules/@reduxjs/toolkit/dist/createSlice'. This is likely not portable. A type annotation is necessary.ts(2742)

Caused by

export const accountActions = slice.actions;

Simply spreading the actions "fixed' it .

// Spread "fixes" TS2742 error
export const accountActions = { ...slice.actions };

This feels similar, but no such workarounds existed for the errors with store. Because we are unable to find workarounds for this (and trying to annotate with EnhancedStore is cumbersome to the point where it's impractical) we are unable to upgrade to RTK 2.0

[chrishoage]

Making this a separate comment so any interested parties will be notified of this.

I discovered that simply importing all types will fix most of these errors. The only one it won't fix is the actions one outlined in the above comment.

import type * as rtk from "@reduxjs/toolkit";

Including this in any file which gives you TS2742 errors when using "declaration": true in your TSConfig (or it gets added for you during type bundle generation) will help typescript get all the needed types in scope, and using import type should prevent all of RTK being included in your bundle.

[Antignote]

I recently ran into this problem as well, any updates on the issue?

The solution provided by @chrishoage worked for me, but is it the correct solution?

I'm developing a npm package and did follow the official documentation for nextjs / typescript and ran into this problem.

[chrishoage]

We ended up aborting our upgrade because the work-round I highlighted above didn't work in some cases. Ultimately some types were not exported and typescript couldn't reconcile this.

I did notice that Typescript 5.5 mentions this error in particular in an upcoming release. I have not tested to see if it helps this situation at all

https://devblogs.microsoft.com/typescript/announcing-typescript-5-5-beta/#consulting-packagejson-dependencies-for-declaration-file-generation

microsoft/TypeScript#42873

[markerikson]

Sorry we haven't had time to look at this. Can folks post some full repo projects that show this happening?

[Antignote]

Sorry, I'm not able to publish the repo since it's a company repo where this issue occours.
@chrishoage is your repo public even tho you aborted the upgrade?

Let me know if it would help if I could upload something else, like ts config or what else.

But the issue occurs for every file which exports any kind of function that has types tied to redux toolkit for me.
The package is within a Nx monorepo

The error is only shown att compile time, I'm using tsc to compile the package

[ryuujo1573]

Sorry we haven't had time to look at this. Can folks post some full repo projects that show this happening?

Hi, please let me provide a humble example of such use case:
ryuujo1573/rtk-ts2742-demo

Thank you for your time!