Front-end programming environment configuration record

Due to work reasons, I changed to a new desktop computer and needed to continue working on the previous VUE project, so I installed VSCode , node.js (with npm, and then installed webpage), and git on the computer .
(Refer to CSDN favorites and Mr. Kang Wenchang's video [vscode nanny-level tutorial and commonly used plug-ins, Re01 compulsory part programming environment configuration] https://www.bilibili.com/video/BV1k34y1Y7xk/?share_source=copy_web&vd_source=da0456ac2eae07c9a7f7947184b9a437)

I found that the version of nodejs may be installed too high, so that the previous project cannot be run, so I changed to a lower version, and it will be fine after the change. I found that it is not necessary to configure nodejs so hard, it should be possible to directly install nvm to manage nodejs, environment variables and so on will be automatically changed, and the high and low versions can be switched freely, which is quite convenient. On the contrary, there may be some redundancy in the environment variable now, and I dare not delete it casually. [At present, it is found that the installed webpack address is in D:\nvm\v12.2.0\node_global\node_modules\webpack, but not in D:\nvm\v12.2.0\node_modules, so the environment variables should also be changed. In short, you can find it later good】

When using nvm to install node for the first time, it may be due to network reasons, npm did not follow the installation, (npm can be installed automatically when node is installed normally) and execute the uninstall command to reinstall with nvm.

Git only needs to configure the user name and email address, set the public key in gitee, and then set the address in VSCode.

Problems found during labelImg installation

Because VS is installed under the Administrator account, some things in python may not be adjusted under the user account, and it will not be installed properly.

Guess you like

Origin blog.csdn.net/weixin_47227105/article/details/128942548