After composer installation, the plug-in is treated as a GIT submodule (GIT subproject)

Using the YII2 framework, I am used to using composer to install plug-ins. After installation, I found that the plug-in directory was treated as a GIT sub-project, and the tool holder was submitted to the project's GIT, which was just an empty directory.

There are a few small questions;
1. Does everyone ignore the vendor when it comes to git for online projects? This feels inconvenient for both collaboration and deployment, mainly because composer is also a problem in China.
2. If this happens, you don’t want to ignore the vendor folder and want to remove the recognition of this sub-project. How should you do it?

Reply content:

Using the YII2 framework, I am used to using composer to install plug-ins. After installation, I found that the plug-in directory was treated as a GIT sub-project, and the tool holder was submitted to the project's GIT, which was just an empty directory.

There are a few small questions;
1. Does everyone ignore the vendor when it comes to git for online projects? This feels inconvenient for both collaboration and deployment, mainly because composer is also a problem in China.
2. If this happens, you don’t want to ignore the vendor folder and want to remove the recognition of this sub-project. How should you do it?

You must have selected the dev-master tag. The main reason is this.

1. Under normal circumstances, of course, vender should be ignored. Usually it is done locally when developing, and then composer updates on the server when publishing. The vendor will not be published as a file.
2. I’m not sure what the problem is. There is no add in git?

Modify .gitignore and delete vendor/ and it should be fine