A few days ago, everything was normal for the project. Yesterday, it was suddenly full of errors. Even if I got the version from half a year ago, I reported the same error.

problem description

suddenly there are a lot of deprecate warnings

the environmental background of the problems and what methods you have tried

upgrade the corresponding dependencies in turn

related codes

/ / Please paste the code text below (do not replace the code with pictures)

peerDependencies WARNING extract-text-webpack-plugin@^2.0.0 requires a peer of webpack@^2.2.0 but webpack@3.12.0 was installed
peerDependencies WARNING babel-loader@^6.4.1 requires a peer of webpack@1 || 2 || ^2.1.0-beta || ^2.2.0-rc but webpack@3.12.0 was installed
peerDependencies WARNING eslint-config-google@^0.9.1 requires a peer of eslint@>=4.1.1 but eslint@3.19.0 was installed
deprecate babel@^6.23.0 In 6.x, the babel package has been deprecated in favor of babel-cli. Check https://opencollective.com/babel to support the Babel maintainers
deprecate autoprefixer-loader@2.1.0  autoprefixer-core@5.2.1  browserslist@~0.4.0 Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
deprecate babel-preset-es2015@^6.9.0 ????  Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
deprecate css-loader@0.23.1  cssnano@3.10.0  autoprefixer@6.7.7  browserslist@^1.7.6 Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
deprecate html-loader@0.3.0  html-minifier@0.7.2  cli@0.6.6  glob@3.2.11  minimatch@0.3 Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
deprecate vue-loader@11.3.4  js-beautify@1.8.6  editorconfig@0.15.0  @types/commander@^2.11.0 This is a stub types definition for commander (https://github.com/tj/commander.js). commander provides its own type definitions, so you don"t need @types/commander installed!
deprecate less@2.7.3  request@2.81.0  hawk@3.1.3  hoek@2.x.x The major version is no longer supported. Please update to 4.x or newer
Recently updated (since 2018-10-01): 11 packages (detail see file D:\\test\b\node_modules\.recently_updates.txt)
  Today:
     autoprefixer-loader@2.1.0  autoprefixer-core@5.2.1  caniuse-db@^1.0.30000214(1.0.30000890) (10:37:39)
     babel-preset-env@1.7.0  browserslist@3.2.8  caniuse-lite@^1.0.30000844(1.0.30000890) (11:32:34)
 All packages installed (1068 packages installed from npm registry, used 27s, speed 335.87kB/s, json 908(8.72MB), tarball 0B)

what result do you expect? What is the error message actually seen?

and the css under a certain route on the page is lost, and hundreds of lines of css style code are lost in the packaging process, causing the table to be squeezed into a pile, but deleting the dependency and re-pulling the dependency under my colleague"s computer runs normally without any errors, including the deformation of the table on my page, but the colleague"s is also normal. His node npm webpack webpack-cli and I both have the same version number. Mine is still the same error

.

how many years ago is your project? There are many problems that need to be paid attention to in js project upgrade, and the library version is particularly important. If there are a lot of mistakes now, there is a good chance that there will be problems with the version of the library. For example, if you use MongoDB's npm package, there is a conflict between the previous version and the current version, including the way to connect to the database, so if you simply upgrade the package, it won't work at all. If the project has been backed up before, use the backup first, and then check the log, that depends on the version of the library to see if there is something wrong with the writing and the code needs to be changed.
there are two points for the js project, including less citation of third-party libraries, upgrade and maintenance. Check the version log of the library before upgrading, and then upgrade if the usage has not changed.
be sure to back up before upgrading!

Menu