Currently, I am working on a project structured like this:
my_project
|
|
|
|
\----my_submodule
|
|
|
\----package.json
\----tsconfig.json
|
|
|
\----package.json
\----tsconfig.json
It's important to note that my_project/package.json and my_project/my_submodule/package.json are the same
{
"name": "my_project",
"version": "1.0.0",
"main": "handler.js",
"scripts": {
"lint": "eslint . --ext .ts,.tsx",
"migration:generate": "ts-node -r tsconfig-paths/register ./node_modules/.bin/typeorm migration:generate -p -d src/local-data-source.ts src/migration/migrations",
"migration:up": "ts-node -r tsconfig-paths/register ./node_modules/.bin/typeorm migration:run -d src/local-data-source.ts",
"migration:list": "ts-node -r tsconfig-paths/register ./node_modules/.bin/typeorm migration:show -d src/local-data-source.ts",
"migration:down": "ts-node -r tsconfig-paths/register ./node_modules/.bin/typeorm migration:revert -d src/local-data-source.ts",
"db:diagram": "ts-node -r tsconfig-paths/register ./node_modules/.bin/typeorm-uml src/ormconfig.json"
},
"dependencies": {
"pg": "^8.8.0",
"reflect-metadata": "^0.1.13",
"typeorm": "^0.3.9"
},
"devDependencies": {
"@types/node": "^16.11.10",
"@typescript-eslint/eslint-plugin": "^3.6.0",
"@typescript-eslint/parser": "^3.6.0",
"eslint": "^7.4.0",
"eslint-config-airbnb-base": "^14.2.0",
"eslint-import-resolver-alias": "^1.1.2",
"eslint-plugin-import": "^2.22.0",
"eslint-plugin-jest": "^23.18.0",
"eslint-plugin-module-resolver": "^0.17.0",
"eslint-plugin-prettier": "^3.1.4",
"ts-node": "10.7.0",
"tsconfig-paths": "^4.1.0",
"typescript": "4.5.2",
"typescript-eslint": "^0.0.1-alpha.0"
},
"config": {
"typeorm": {
"migrations_path": "src/migration"
},
"commitizen": {
"path": "./node_modules/cz-conventional-changelog"
}
}
}
After running npm install, it seems that typeorm is being installed under my_project/my_submodule
. How can I ensure that it gets installed under just my_project
? It seems to work correctly for team members not using VSCode, so why isn't it consistent for me? I attempted adding rootDir
to both directories but that didn't resolve the issue.