Skip to content
This repository has been archived by the owner on Oct 17, 2024. It is now read-only.

peer deps conflict with nest ^9 and @aginix/[email protected] #659

Open
ZionSimilarWeb opened this issue Oct 11, 2022 · 1 comment
Open

Comments

@ZionSimilarWeb
Copy link

ZionSimilarWeb commented Oct 11, 2022

When trying to run a docker with nest ^9 and @aginix/[email protected] you get the next error
Could not resolve dependency:
#8 3.775 npm ERR! peer @nestjs/common@"^7.1.2" from @aginix/[email protected]
#8 3.776 npm ERR! node_modules/@aginix/nestjs-firebase-admin
#8 3.776 npm ERR! @aginix/nestjs-firebase-admin@"^2.2.0" from the root project

my package json is this

{
"name": "my-org",
"version": "0.0.0",
"license": "MIT",
"scripts": {
"start": "nx serve",
"build": "nx build",
"test": "nx test"
},
"private": true,
"dependencies": {
"@aginix/nestjs-firebase-admin": "^2.2.0",
"@log4js-node/gelf": "^1.0.2",
"@nestjs/class-validator": "^0.13.4",
"@nestjs/common": "^9.0.0",
"@nestjs/core": "^9.0.0",
"@nestjs/platform-express": "^9.0.0",
"reflect-metadata": "^0.1.13",
"rxjs": "^7.0.0",
"tslib": "^2.3.0"
},
"devDependencies": {
"@nestjs/schematics": "^9.0.0",
"@nestjs/testing": "^9.0.0",
"@nrwl/cli": "14.8.3",
"@nrwl/eslint-plugin-nx": "14.8.3",
"@nrwl/jest": "14.8.3",
"@nrwl/linter": "14.8.3",
"@nrwl/nest": "14.8.3",
"@nrwl/node": "14.8.3",
"@nrwl/nx-cloud": "latest",
"@nrwl/workspace": "14.8.3",
"@types/jest": "28.1.1",
"@types/node": "16.11.7",
"@typescript-eslint/eslint-plugin": "^5.36.1",
"@typescript-eslint/parser": "^5.36.1",
"eslint": "~8.15.0",
"eslint-config-prettier": "8.1.0",
"jest": "28.1.1",
"jest-environment-jsdom": "28.1.1",
"nx": "14.8.3",
"prettier": "^2.6.2",
"ts-jest": "28.0.5",
"ts-node": "10.9.1",
"typescript": "~4.8.2"
}
}

and my docker file is this

FROM node:16-alpine
ENV APP_NAME=api
COPY --chown=node:node ./ ./app
WORKDIR ./app
RUN npm install
RUN echo "DONE!!!!"

its an NX workspace
my docker command is

docker build --progress=plain -f ./apps/api/Dockerfile . -t api-test

BTW - on node 14 it seems to be working fine

@M4R14
Copy link

M4R14 commented Feb 6, 2023

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants