adminjs icon indicating copy to clipboard operation
adminjs copied to clipboard

[Bug]: Conflict with SuperTokens peer dependency prevents installation

Open Anthony-Perriolat opened this issue 7 months ago • 0 comments

Contact Details

No response

What happened?

Hello team,

I'm trying to install @adminjs/nestjs and @adminjs/prisma in my NestJS project, but the installation fails due to a peer dependency conflict with supertokens-nestjs.

To Reproduce

Start a new NestJS project.

Install supertokens-node and supertokens-nestjs:

npm install [email protected] [email protected]

(Note: This is a working configuration for SuperTokens.)

Attempt to install the AdminJS packages: Bash

npm install adminjs @adminjs/nestjs

The installation fails with the following ERESOLVE error: Bash

    npm ERR! code ERESOLVE
    npm ERR! ERESOLVE could not resolve
    npm ERR!
    npm ERR! While resolving: [email protected]
    npm ERR! Found: [email protected]
    npm ERR! node_modules/supertokens-node
    npm ERR!   supertokens-node@"^23.0.1" from the root project
    npm ERR!
    npm ERR! Could not resolve dependency:
    npm ERR! peer supertokens-node@"^21.1.0 || ^22.1.0" from [email protected]
    npm ERR! node_modules/supertokens-nestjs
    npm ERR!   supertokens-nestjs@"^0.0.5" from the root project

Expected behavior

The AdminJS packages should install without dependency conflicts or have a version of supertokens-nestjs that supports the latest supertokens-node version.

Desktop (please complete the following information):

OS: [Votre système d'exploitation, ex: macOS, Windows, Ubuntu]

Node.js version: [La version de Node.js que vous utilisez, ex: v18.17.1]

NPM version: [La version de NPM que vous utilisez, ex: 9.6.7]

Additional context

The error indicates that [email protected]'s peerDependency is not compatible with [email protected]. This is likely a conflict between AdminJS's dependencies and SuperTokens' dependencies, or a specific version of a package that is being pulled in.

Thank you for your help!

Bug prevalence

All time

AdminJS dependencies version

"dependencies": { "@apollo/server": "^4.12.2", "@graphql-tools/schema": "^10.0.25", "@nestjs/apollo": "^13.1.0", "@nestjs/common": "^11.0.1", "@nestjs/core": "^11.0.1", "@nestjs/graphql": "^13.1.0", "@nestjs/platform-express": "^11.0.1", "@prisma/client": "^6.12.0", "apollo-server-express": "^3.13.0", "class-transformer": "^0.5.1", "graphql": "^16.11.0", "graphql-redis-subscriptions": "^2.7.0", "graphql-subscriptions": "^3.0.0", "graphql-tools": "^9.0.20", "graphql-type-json": "^0.3.2", "graphql-ws": "^6.0.6", "ioredis": "^5.6.1", "prisma-graphql-type-decimal": "^3.0.1", "reflect-metadata": "^0.2.2", "rxjs": "^7.8.1", "subscriptions-transport-ws": "^0.11.0", "supertokens-nestjs": "^0.0.5", "supertokens-node": "^23.0.1" }, "devDependencies": { "@eslint/eslintrc": "^3.2.0", "@eslint/js": "^9.18.0", "@graphql-codegen/cli": "^5.0.7", "@graphql-codegen/typescript": "^4.1.6", "@graphql-codegen/typescript-resolvers": "^4.5.1", "@nestjs/cli": "^11.0.0", "@nestjs/schematics": "^11.0.0", "@nestjs/testing": "^11.0.1", "@swc/cli": "^0.6.0", "@swc/core": "^1.10.7", "@types/express": "^5.0.0", "@types/jest": "^29.5.14", "@types/node": "^22.10.7", "@types/supertest": "^6.0.2", "eslint": "^9.18.0", "eslint-config-prettier": "^10.0.1", "eslint-plugin-prettier": "^5.2.2", "globals": "^16.0.0", "jest": "^29.7.0", "prettier": "^3.4.2", "prisma-nestjs-graphql": "^21.2.0", "source-map-support": "^0.5.21", "supertest": "^7.0.0", "ts-jest": "^29.2.5", "ts-loader": "^9.5.2", "ts-node": "^10.9.2", "tsconfig-paths": "^4.2.0", "typescript": "^5.7.3", "typescript-eslint": "^8.20.0" },

What browsers do you see the problem on?

No response

Relevant log output


Relevant code that's giving you issues


Anthony-Perriolat avatar Aug 04 '25 17:08 Anthony-Perriolat