Add Composer.json to project

Great. There was also a pull request on github. Maybe we can use something from there.

+++ b/composer.json
@@ -0,0 +1,33 @@
+      "name": "John McCormick",
+      "homepage": "drupal.org/u/neardark",
+      "role": "Maintainer"

chrfritsch is a maintainer too now, John has not been very active, so I think it's best to put chrfritsch here.

Committed, thanks.

From https://getcomposer.org/doc/04-schema.md#suggest :

suggest#

Suggested packages that can enhance or work well with this package. These are just informational and are displayed after the package is installed, to give your users a hint that they could add more packages, even though they are not strictly required.

The format is like package links above, except that the values are free text and not version constraints.

Example:

{
"suggest": {
"monolog/monolog": "Allows more advanced logging of the application flow",
"ext-xml": "Needed to support XML format in class Foo"
}
}

so the respond.js should not be a suggestion, because it does not "enhance or work well" with this module.
DropzoneJS library is a actually a requirement for this module to function, and this have nothing to do with the fact that installer-path for libraries should need to be setup after from a project root composer.json

A Drupal 8 site should be easily installed and extended with the "composer create-project ..." command and "composer require ...", without the need to go and manually download required libraries. That's the main purpose of composer, if not we could just stick to drush dl.

So when you install the Drupal 8 project with composer and want to add this module,
"composer require drupal/dropzonejs " and "composer update" should be all.

I agree and share the same frustration with you, it should be easy.

But in this case we are not dealing with a php lib that lives on packegist, it's a js library that lives on a separate repository. And drush dl didn't support pulling this kind of dependencies either.

There are third party libraries that one can include in the composer file, that then download js dependencies, but I don't think I saw much Drupal projects using them. I would be happy to hear more about that though.

Since in this specific case dropzonejs is an integration module for the dropzone.js library, clearly listed as a requirement and linked from the module page to the library/project github page, what I don't understand is why the composer.json file included with the drupal module dropzonejs does not contain something like this:

    "repositories": [
        {
            "type": "package",
            "package": {
                "name": "enyo/dropzone",
                "version": "4.3.0",
                "type": "drupal-library",
                "source": {
                    "url": "https://github.com/enyo/dropzone",
                    "type": "git",
                    "reference": "origin/master"
                }
            }
        },
    "extra": {
        "installer-paths": {
            "web/libraries/{$name}": [
              "type:drupal-library",
              "enyo/dropzone"
            ],
        }

web/libraries/{$name} is the path that drupal8 project is using.

Then if any distribution wants to include the module in the distribution, the distribution global composer.json should override the module defined "installer-paths" to something like docroot/libraries/{$name} or sites/default/files/libraries/{name} or whatever they desire

Actually the code above is an example from what I included in the Thunder ( https://www.drupal.org/project/thunder ) distribution's main composer.json managing to download the required libraries without nodejs, npm and bower. I guess the distribution is using nodejs, npm and bower to download them ( correct me if I'm wrong)