Reactjs 使用package.json响应引导数据采集器问题
我的npm软件包安装程序有一个大问题。它一直在工作,但我删除了package-lock.json文件,现在根本不工作。我似乎无法运行它,目前我只能提供如下所示的pakage.json文件和我的npm日志,其中给出以下错误: Npm日志 My package.jsonReactjs 使用package.json响应引导数据采集器问题,reactjs,npm,Reactjs,Npm,我的npm软件包安装程序有一个大问题。它一直在工作,但我删除了package-lock.json文件,现在根本不工作。我似乎无法运行它,目前我只能提供如下所示的pakage.json文件和我的npm日志,其中给出以下错误: Npm日志 My package.json { "private": true, "scripts": { "dev": "npm run development"
{
"private": true,
"scripts": {
"dev": "npm run development",
"development": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
"watch": "npm run development -- --watch",
"watch-poll": "npm run watch -- --watch-poll",
"hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --disable-host-check --config=node_modules/laravel-mix/setup/webpack.config.js",
"prod": "npm run production",
"production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"
},
"devDependencies": {
"@babel/preset-react": "^7.12.1",
"axios": "^0.19",
"babel-plugin-transform-class-properties": "^6.24.1",
"babel-preset-react": "^6.24.1",
"bootstrap": "^4.0.0",
"browser-sync": "^2.26.13",
"browser-sync-webpack-plugin": "^2.2.2",
"cross-env": "^7.0",
"jquery": "^3.2",
"laravel-mix": "^5.0.1",
"lodash": "^4.17.19",
"popper.js": "^1.12",
"react": "^16.2.0",
"react-dom": "^16.14.0",
"resolve-url-loader": "^3.1.0",
"sass": "^1.15.2",
"sass-loader": "^8.0.0"
},
"dependencies": {
"@crystallize/react-growl": "^3.2.0",
"@material-ui/core": "^4.11.3",
"@material-ui/icons": "^4.11.2",
"final-form": "^4.20.1",
"final-form-arrays": "^3.0.2",
"framer-motion": "^2.9.4",
"google-map-react": "^2.1.8",
"google-maps-react": "^2.0.6",
"google-timezone-api": "^1.0.1",
"i": "^0.3.6",
"leaflet": "^1.7.1",
"moment": "^2.29.1",
"moment-timezone": "^0.5.32",
"npm": "^6.14.8",
"query-string": "^6.14.1",
"react-bootstrap": "^1.5.2",
"react-bootstrap-date-picker": "^5.1.0",
"react-bootstrap-typeahead": "^5.1.4",
"react-content-loader": "^5.1.4",
"react-create-class": "^1.0.0",
"react-data-table": "^0.1.0",
"react-data-table-component": "^6.11.5",
"react-datepicker": "^3.3.0",
"react-dates": "^21.8.0",
"react-device-detect": "^1.14.0",
"react-dropzone": "^11.2.3",
"react-feather": "^2.0.8",
"react-final-form": "^6.5.1",
"react-final-form-file-field": "0.0.6",
"react-google-places-autocomplete": "^3.0.0",
"react-growl": "^0.1.2",
"react-helmet": "^6.1.0",
"react-image-crop": "^8.6.6",
"react-lazyload": "^2.6.5",
"react-leaflet": "^2.7.0",
"react-notifications": "^1.7.2",
"react-parallax": "^3.1.2",
"react-phone-number-input": "^3.1.16",
"react-places-autocomplete": "^7.3.0",
"react-redux": "^7.2.1",
"react-router-dom": "^5.2.0",
"react-router-redux": "^4.0.8",
"react-select": "^3.1.0",
"react-slick": "^0.27.12",
"react-table": "^6.11.5",
"react-table-v6": "^6.8.6",
"react-toast-notifications": "^2.4.0",
"redux": "^4.0.5",
"redux-thunk": "^2.3.0",
"slick-carousel": "^1.8.1",
"styled-components": "^5.2.0"
},
"babel": {
"presets": [
"@babel/preset-env",
"@babel/preset-react"
],
"plugins": [
"@babel/plugin-proposal-class-properties"
]
}
}
看起来我回答了我自己的问题如下:
npm安装--旧式对等dep
如果有人能说明这一点,那么这一技术在生产和未来使用是否安全。谢谢。react引导日期选择器正在寻找比您安装的版本旧得多的react引导版本。插入符号(^)仅允许小版本更新。0.x到1.x是一个主要的版本更新
除了降级react-bootstrap,或者用另一个库替换react-bootstrap日期选择器之外,您没有什么可以做的。在package.json中指定的
react-bootstrap
版本之间存在版本冲突,react bootstrap日期选择器
指定它需要的react bootstrap
版本
您的package.json列表
“反应引导”:“^1.5.2”
在最新的react引导日期选择器中,它列出
“反应引导”:“^0.31.0”
胡萝卜符号(^
)允许npm安装最新的次要版本(由三部分组成的版本字符串中的第二个数字),但从不更改主要版本号(版本字符串中的第一个数字)。这意味着^0.31.0
版本不能自动增加到1.0.0
(下一个主要版本)或更高版本
我建议更改package.json以指定:“react bootstrap”:“^0.32.0”
。但是,您应该知道,它将安装相当旧版本的react bootstrap
或者,您可能还想四处寻找更新的日期选择器包,因为它看起来不像react bootstrap date picker
在过去四年中更新过。它依赖于较旧版本的react bootstrap
(约4年前)。与最新版本的Bootstrap 4和5相比,它可能也已经过时了。谢谢@user2867288查看底部的我的解决方案它解决了问题,我只是想知道这是否只是一个临时的黑客行为。。这并不理想,如果您还没有将package-lock.json提交到repo,那么您需要确保在合并过程中对其进行正确管理。我会优先更新你的应用程序,这样你就不会有相互冲突的对等依赖关系。让这些家伙更新他们的图书馆!