Problems installing NPM-assets

[jeabakker]

since a few days i get errors when trying to update/install npm-asset dependencies

It's trying to update to npm-asset/moment v2.22.1

  - Removing npm-asset/moment (2.22.0)

  [InvalidArgumentException]
  Unknown downloader type: npm-signature. Available types: git, svn, fossil, hg, perforce, zip, r
  ar, tar, gzip, xz, phar, file, path.

I don't know if this is the correct place to report this, if not i'm sorry.

composer --version
Composer version 1.6.4 2018-04-13 12:04:24

and

fxp/composer-asset-plugin v1.4.2 NPM/Bower Dependency Manager for Composer

[holtkamp]

Also got some issues since a few days / since composer 1.6.4: it seems a specific package is removed without any sign. After a composer update no "removals" were reported but the composer.lock file is changed and a package is removed. Reported this in a separate issue, not sure it is related to this issue: #322

[Zaporozhec7]

I have same issue, with same package "npm-asset/moment" of version 2.21.0

[hypeJunction]

Having this issue as well now with npm-asset/formdata-polyfill
For some reason it's trying to remove it first, then I get the exception

[rob006]

The reason: https://blog.npmjs.org/post/172999548390/new-pgp-machinery

I described workaround at Stack Overflow, but it will be a pain if you have multiple npm packages broken by this.

@SilverFire @hiqsol This affects also asset-packagist - just check dist URL of last release of https://asset-packagist.org/package/npm-asset/moment

[Zaporozhec7]

I have created pull request with fix for this issue, but it fail test, since my fix disallow other dist types than supported by Composer, but in test data used dist type "type" (https://github.com/fxpio/composer-asset-plugin/blob/master/Tests/Converter/NpmPackageConverterTest.php#L192).

I think filter out all unknown by Composer types is right solution, since this can help to avoid new issues like this if next time npm will add another one new field to dist information

[twisted1919]

Any updates on this ? This simply left our apps broken...

[sicutdeux]

Bump here with npm-asset/load-google-maps-api (1.2.1)

[sicutdeux]

editing the composer.json file and removing the dependency in the require section, then using "composer require" it does work, but that's not a solution really.

[SDKiller]

@sicutdeux

Another workaround - it worked for me (compared with @rob006 described - you need not locate release tarball):

    "config": {
        ...
        "fxp-asset": {
             ...
            "repositories": [
                {
                    "name": "npm-asset/html5sortable",
                    "type": "npm-vcs",
                    "url": "git@github.com:lukasoppermann/html5sortable.git"
                }

Note that you add package to repositories in fxp-asset entry in config, not to repositories in composer.json root.

[jeabakker]

Still no permanent solution (after 1 month)?? @francoispluchino

[nimer-]

Yeah - it is surprising. A lot of workarounds, 1 PR that solves it, but we have no real permanent solution. That's a bummer to say the least.

[francoispluchino]

@jeabakker @nimer- The PR #323 still has errors in the tests, that's why it is not merged. But you can contribute by proposing a valid PR. A help is always appreciated.

[twisted1919]

@francoispluchino

he PR #323 still has errors in the tests, that's why it is not merged. But you can contribute by proposing a valid PR. A help is always appreciated.

This sounds easy in theory, right? But think a bit, we are developers doing other things and we have no experience to work on your plugin, getting involved would mean maybe hours to only learn it's internals.

If you have problem finding the time, please don't throw it on your user base, instead, set a donation page, let us pay for your time and fix the issue if possible. This is how things work, i would gladly contribute to see this issue solved.

Just my two cents.