This is unusual pull request, but I really would like that this would be included in the project, because this will add a possibility to use node-composer with such tools like Dependabot.

This pull request adds a GitHub Action that runs every 24 hours and checks if new NodeJS version is released. If so, it will release new version for node-composer with similar version number like NodeJS. For example if GitHub Action detects if there was a new NodeJS 14.15.1 released it automatically releases node-composer with v14.15.1-1 tag.

If node-composer is included in other PHP project and than newer NodeJS 14.15.2 is released. Such tools like Dependabot will notify project owner about possible upgrade. If owner accepts this change, newer NodeJS version also for that project will be installed.

So basically this change adds possibility easier to upgrade to newer NodeJS when is possible.

This is how these automatically releases looks on GitHub:

There is one possible issue with this pull request. Master branch should not contain any dev code. Because every 24 hours automatic release will be generated. But from what I see, I don't think that could happen very often for this repo.

I really hope this change will be included. For me that would be very useful thing and I think for many others too.

It seems that ZipArchiver on Windows with PHP 7.0 can't extract correctly node archives, so I bumped minimal required PHP version in composer.json to 7.1

It seems that some GitHub machines returns architecture in uppercase, but on my localhost I see only lowercase variants, so change makes sure that mapping allways works as architecture value is in lowercase.

After running CI tests I found out that amd64 and i586 values are needed to be added into ArchitectureMap file, because some GitHub machines returns these values instead of x64 or x86. So, here is the fix.

After merging this every time after somebody creates pull request to the repository new Github Action called 'Tests' stars thats will test if new changes will work good enough with PHP 7.1-7.4, Composer 1-2, windows/ubuntu/macos (right now only works X86/X64 architectures).

And this is an example how these tests could look in GitHub:

description field in composer.json if type is not library is required. So I added.

Also, from now it's possible to use this little composer-plugin in projects with never symfony process versions.

symfony/process in 3.x and below expects a string, but in 4.x and up expects an array. This will fix anyone using 4 and up, and should be split out into a different base version.

This fix should be tagged in a 2.x version

fixes #16

This seems to be broken when using Composer 2.3, but the underlying issue is the Symfony Process 5.4 library that expects an array, while this package is using the 2.x version.

https://github.com/symfony/process/blob/5.4/Process.php#L143

In Process.php line 143:

  [TypeError]
  Argument 1 passed to Symfony\Component\Process\Process::__construct() must be of the type array, string given, called in /project/vendor/mariusbuescher/node-composer/src/Installer/NodeInstaller.php on line 84


Exception trace:
  at phar:///opt/homebrew/Cellar/composer/2.3.2/bin/composer/vendor/symfony/process/Process.php:143

Similar to #14 but instead of having multiple version conflicts, correct nodejs and yarn versions are detected from imponeer/composer-nodejs-installer and imponeer/composer-yarn-installer package data. So, if any of these packages are installed in project, config values will be overwritten from these packages data.

F.e., if project has such composer.json:

{
  "name": "dummy/dummy",
  "description": "Dummy project to test if configuration works",
  "type": "project",
  "require": {
    "mariusbuescher/node-composer": "@dev",
    "imponeer/composer-nodejs-installer": "1.0.0"
  }
}

Node 1.0.0 will be installed

or if project has such composer.json:

{
  "name": "dummy/dummy",
  "description": "Dummy project to test if configuration works",
  "type": "project",
  "require": {
    "mariusbuescher/node-composer": "@dev",
    "imponeer/composer-nodejs-installer": "1.0.0",
    "imponeer/composer-yarn-installer": "1.0.0",
  }
}

Node 1.0.0 and yarn 1.0.0 will be installed

or if project has such composer.json:

{
  "name": "dummy/dummy",
  "description": "Dummy project to test if configuration works",
  "type": "project",
  "require": {
    "mariusbuescher/node-composer": "@dev",
    "imponeer/composer-yarn-installer": "1.0.0",
  }
}

Latest nodejs and yarn 1.0.0 version will be installed

or if such composer.json:

{
  "name": "dummy/dummy",
  "description": "Dummy project to test if configuration works",
  "type": "project",
  "require": {
    "mariusbuescher/node-composer": "@dev",
    "imponeer/composer-yarn-installer": "1.0.0",
  },
  "extra": {
        "mariusbuescher": {
            "node-composer": {
                "node-version": "6.11.0"            
            }
        }
    }
}

Yarn 1.0.0 and node 6.11.0 will be installed

However if both ways are defined, data from packages (not extras will take a priority). So, that's means that such composer.json config:

{
  "name": "dummy/dummy",
  "description": "Dummy project to test if configuration works",
  "type": "project",
  "require": {
    "mariusbuescher/node-composer": "@dev",
    "imponeer/composer-yarn-installer": "1.0.0",
  },
  "extra": {
        "mariusbuescher": {
            "node-composer": {
                "yarn-version": "0.11.0" 
                "node-version": "6.11.0" 
            }
        }
    }
}

This would install yarn 1.0.0 and node 6.11.0

Of cource it will be possible to use composer version constraints for such new functionality. So, it would be easier to update package nodejs versions.

Yeah, I know this is a bit hardcoded that is not very good practice but I think this would be maybe a bit better way to solve this problem than #14 and this doesn't required to solve a big problem how to handle multiple installed nodejs and yarn versions. What do you think?

This will let to define config not only in project level but also in also in dependencies.

If there are multiple dependencies, with different node or yarn versions, max versions will be selected (yeah I, know, that would be awesome to have multiple nodejs and/or yarn versions installed, but I think this requires some huge changes... so at least something for now...)

Project level config definitions takes priority. That means if these are found, all configs in dependencies will be ignored.

Accepting this change let others to create libraries that depends on node-composer that could be used in projects. For example, a package that automatically bumps owen version everytime new nodejs is released (similar thing that I tried to achieve with #2 pull request). Or some package that automatically tries to deal with front-end npm assets management.

Note: #10 must be merged first to make sure that all platform tests succeeds.

Release drafter is amazing GitHub Action to easy maintan changes list between releases - You don't need anymore to walk between all pull requests and see what changed. The list will be generated automatically!

This pull request adds this amazing tool. I think it could save many your free time when you are doing releases.

I created issue from comment on my pull request:

Sorry, it is still early though. I like your idea, but I am not sure if I will continue to maintain this project. Actually this hasn't been touched in years. If you are interested, you can continue maintaining it.

Originally posted by @mariusbuescher in https://github.com/mariusbuescher/node-composer/pull/2#issuecomment-719373183