Add a release for masonry_views 4.x

Indeed... Is anybody knows when it will be ok? Or maybe is it easy to install it with Git ?

Apparently there is a solution here.

https://www.drupal.org/project/masonry_views/issues/3288460#comment-1510... 📌 Automated Drupal 10 compatibility fixes Fixed

The bit that confused me is that Masonry Views is a submodule but still needs to be installed separately?

Looking forward to official release to test this with Drupal 10.

My guess is it might be possible to install js dependencies masonry and imagesloaded into /libraries folder if you are already using composer-installers-extender without having to also install wikimedia/composer-merge-plugin

e.g. composer require 'bower-asset/masonry:^4.2.2'

https://www.danlobo.co.uk/article/using-composer-manage-your-js-dependen...

Ok tried and failed to install with composer using the above suggestion. Also their seems to be an issue on drupalcode.org where downloads seems to redirect me to the home page on drupal.org?

Just ended up cloning the module and copying the files across to my codebase for now, taking care to remove the .git folder

Working for me out of the box for me running drupal 10.1.1 with bootstrap base theme.

Actually composer require 'bower-asset/masonry:^4.2.2' does also work, just need to specify as installer type and installer path e.g.

   "installer-paths": {
            "web/core": [
                "type:drupal-core"
            ],
            "web/libraries/{$name}": [
                "type:drupal-library",
                "type:npm-asset",
                "type:bower-asset"
            ],
...

and

    "extra": {
        "drupal-scaffold": {
            "locations": {
                "web-root": "web/"
            }
        },
        "installer-types": [
            "npm-asset",
            "bower-asset",
            "drupal-library"
        ],
...

After I updated masonry API to 4.x (configuration change), the purpose is now to make this module compatible with the newest version.

Automatically closed - issue fixed for 2 weeks with no activity.