Recently, a front-end and back-end separation project was implemented using git clone. A problem was encountered during the front-end startup. Node.js was used The NPM run serve command and the yarn run serve command will report an error when starting the front-end project. You have tried to download the dependent node that has been installed_ The modules folder and the whole front-end project still reported this problem. Baidu found the error: command failed: git describe — always, and did not find the corresponding article
Later, I finally found the problem and reported the error because of the environment variable problem of GIT
First, this is the wrong git configuration, which leads to the error: command failed: git describe — always problem
The following is how to correctly configure environment variables. Add CMD after the original path
Then, create a new CMD and enter yarn run serve to run normally. The problem I encountered is solved in this way
Read More:
- [Solved] Error: Cannot find module ‘@vue/cli-shared-utils
- [Solved] Error spawn CMD enoent errno when starting Vue project: – 4058
- [Solved] Vue Compile Error: JavaScript heap out of memory
- package.json Scripts configuration environment variable distinguishes development environment from production environment
- [Solved] error C:\Users\HP\Desktop\VueProject\vue_cli\node_modules\node-sass: Command failed.Exit code: 1
- After Vite starts, it will prompt “network: use ` — host ` to expose”, and the service cannot be accessed through network IP
- NPM run dev runs the Vue project and reports an error: Node Sass does not yet support your current environment
- [Solved] SyntaxError: Cannot use import statement outside a module
- [Solved] ERROR Error: Cannot find module ‘vue-loader-v16/package.json‘
- React project is packaged and set as required Error [How to Solve]
- [Solved] Vue unit test syntax error: unexpected token ‘export‘
- [Solved] NPM err! Cannot read property ‘parent’ of null npm ERR! A complete log of this run can be found in: npm ERR!
- [Solved] Error: ENOENT: no such file or directory, scandir ‘..\node_modules\node-sass\vendor‘
- How to Solve NPM installation -g @view/client Error
- Vue-cli2 sub environment packaging
- How to Solve VUE Error: Mixed spaces and tabs
- How to Solve Vue cli configuration SCSS global variable error
- Vue installs sass loader directly, and node sass reports an error
- Front end initialization Vue element admin error [How to Solve]
- [Solved] Project Package Error: Javascript heap out of memory