Let's imagine a scenario where I have a package.json structured like this:
{
"name": "my-app",
"version": "0.1.0",
"dependencies": {
"@aws-sdk/client-s3": "^3.21.0",
"@testing-library/react": "^11.2.5",
"axios": "^0.22.0",
"credit-card-type": "^8.3.0",
"csstype": "^3.0.8",
"dayjs": "^1.10.4",
"lodash": "^4.17.20",
"mathjax-full": "^3.2.0",
"mathjax-react": "^1.0.6",
"react": "^17.0.2",
},
"proxy": "http://localhost:5000",
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "jest",
"eject": "react-scripts eject",
},
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
}
}
The challenge arises when the dependencies mathjax-react and mathjax-full require
react@"^15.0.0 || ^16.0.0"npm i --force and npm i --legacy-peer-deps, there is a desire to streamline the process without having to use these commands each time new dependencies are installed, especially for the mentioned packages which should be automatically handled during npm i. Exploring options in the .npmrc configuration and related resources did not provide a clear solution. Is there a built-in method within npm to address this issue, or would creating a custom script that parses the package.json and executes individual npm install commands be necessary?
The concern is that without a systematic approach, potential conflicts with future dependencies might go unnoticed.