Vue error log

1. The error Warning: Accessing non-existent property 'cat' of module exports inside circular dependency is reported when building the project.

wrong description

运行 npm run build


building for production...(node:97524) Warning: Accessing non-existent property 'cat' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:97524) Warning: Accessing non-existent property 'cd' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'chmod' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'cp' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'dirs' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'pushd' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'popd' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'echo' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'tempdir' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'pwd' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'exec' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'ls' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'find' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'grep' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'head' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'ln' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'mkdir' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'rm' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'mv' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'sed' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'set' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'sort' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'tail' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'test' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'to' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'toEnd' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'touch' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'uniq' of module exports inside circular dependency
(node:97524) Warning: Accessing non-existent property 'which' of module exports inside circular dependency

Solution:
"shelljs" in package.json: change the version to 0.8.4 and then
re-npm inpm run build

2. WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.

Problem Description:

WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration.output.path: The provided value "./" is not an absolute path!
   -> The output directory as **absolute path** (required).

Solution:
Determine the source of the problem and detect the Webpack configuration file webpack.base.conf.js.
Based on the error message, we can get some tips about the configuration file. Possible error messages include missing required properties, property values ​​of the wrong type, or unsupported configuration options. According to the error message, check the configuration files one by one and make adjustments.