"type" property is missing in composer.json

I will review this one.

Hi everyone, thank you for your contributions!

The type property is automatically set to drupal-module in Drupal.org's packaging script, so I removed it from the composer.json committed to git in ✨ Simplify composer.json Active ... the packaging script runs when I make a release, and the fully-filled-in composer.json makes onto composer.drupal.org and into the zip and tar.gz files.

If you're finding that composer is cloning the module in your project instead of downloading a packaged stable version, then your project's minimum-stability might be set wrong; or you might have a stability override for Sitemap module - removing the stability override might help. I also recommend double-checking that prefer-stable is set to true.

If you need to clone the Sitemap module because you want to develop the module (i.e.: contribute patches or merge requests), then I recommend using ddev's ddev-drupal-contrib add-on. Using ddev-drupal-contrib will get around asking Composer to clone the Sitemap module (i.e.: so composer won't complain about the missing type properly). I apologize for not updating the sitemap module's documentation with instructions as I have done for elasticsearch_connector →

@mparker17
Thank you for helpful reply.
OK, I understood about composer.json.

To follow-up on my last comment, I have now written some documentation on how to set up Sitemap module for local development: https://www.drupal.org/docs/contributed-modules/sitemap/developing-sitem... →