Updating /modules directory file

[samcoppock]

I have noticed that the composer.json file does not have any reference to the /modules directory?

yet when comparing the changes between v 1.2.1 > 1.2.5 there are many changes to files in this directory.

does updating winter via composer somehow update files in the modules directory.

if yes how?

if no - do these files need to be updated when updating the winter version?

[jaxwilko]

Off the top of my head I can't remember where it happens, but anything with the composer type property winter-module will automatically get moved into /modules on install.

This mechanism is the same as the system that moves winter-plugin packages into your plugins dir on install.

Because of this, generally you would gitignore the modules dir and just let composer pull the contents in when you run composer install

[bennothommo]

It happens as part of the composer/installers package that we include with Winter - this PR added support to Composer to put winter-module, winter-plugin and winter-theme packages in the correct directory.

[WebVPF]

graph TB;
    A[modules]-->Backend;
    A-->CMS;
    A-->System;

Loading

Here they are:

winter/composer.json

Lines 34 to 36 in 65c9cd9

	"winter/wn-system-module": "dev-develop",
	"winter/wn-backend-module": "dev-develop",
	"winter/wn-cms-module": "dev-develop",

[LukeTowers]

@samcoppock wintercms/winter is basically a project template, you can think of it as being similar to laravel/laravel. The code is managed in one place in this repository for simplicity, but it gets split out automatically to the winter/wn-*-module repositories / packages which are pulled in via composer.

You should not track the modules/ folder in your git repositories, just like you should not track the vendor folder, nor any plugins that you include via composer.