search

hiqdev / asset-packagist

Asset Packagist
https://asset-packagist.org
BSD 3-Clause "New" or "Revised" License
247 stars 25 forks source link

Weird download link for version 2.3.4 of owl.carousel #80

Closed rodrigoaguilera closed 6 years ago

rodrigoaguilera commented 6 years ago

If you go to https://asset-packagist.org/package/detail?fullname=npm-asset/owl.carousel and try to download version 2.3.4 the link does not take you to the package.

On composer trying to install I get [InvalidArgumentException] Unknown downloader type: npm-signature. Available types: git, svn, fossil, hg, perforce, zip, rar, tar, gzip, xz, phar, file, path

SamMousa commented 6 years ago

This is causing the issue:

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

hiqsol commented 6 years ago

Yep. Here is more: https://github.com/fxpio/composer-asset-plugin/issues/321

webmaster777 commented 6 years ago

This is gonna be a real problem soon, as new versions of npm packages get published.

We cannot get the latest version of codemirror for example: https://asset-packagist.org/package/npm-asset/codemirror

The ZIP url is malformed and results in a 404.

While composer automatically tries to install the new version it will result in an error every time I run composer update:

> composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)                                              
Package operations: 0 installs, 8 updates, 0 removals
  - Removing npm-asset/codemirror (5.36.0)

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

update [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--lock] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [--no-suggest] [--with-dependencies] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [-i|--interactive] [--root-reqs] [--] [<packages>]...
SamMousa commented 6 years ago

@hiqsol are you working on this? If not, will you have time or should we try to make a PR?

hiqsol commented 6 years ago

Actually I thought the problem is going to be solved in composer-asset-plugin. I've seen discussion https://github.com/fxpio/composer-asset-plugin/issues/321 and corresponding PR there: https://github.com/fxpio/composer-asset-plugin/pull/323 If the problem is solved there then it's solved here automatically.

rob006 commented 6 years ago

@hiqsol fxpio/cap was fixed in last release, but asset-packagist is still broken: https://asset-packagist.org/package/npm-asset/moment

hiqsol commented 6 years ago

I need to update (check everything still works). It takes some time.

hiqsol commented 6 years ago

Done update. Looks fine.

Troublesome packages need to be updated (refetched from npm) to become usable. So I updated all the packages mentioned in issues.

All the available packages will be updated automatically. But it will take some days, so if you still come across this error (Unknown downloader type), please update corresponding package manually with pressing 'Fetch updates from Npm' button on asset-packagist.org

In case you don't know which package causes the problem please use `composer update -v' it provides more information. Look for lines like this:

Package operations: 13 install, 0 updates, 0 removals
Installs: npm-asset/ajv-keywords:3.2.0, npm-asset/punycode:v2.1.1, npm-asset/uri-js:4.2.1, npm-asset/fast-deep-equal:2.0.1, npm-asset/ajv:6.5.0, npm-asset/schema-utils:0.4.5, npm-asset/json5:0.5.1, npm-asset/emojis-list:2.1.0, npm-asset/big.js:3.2.0, npm-asset/loader-utils:1.1.0, npm-asset/worker-loader:1.1.1, npm-asset/node-ensure:0.0.0, npm-asset/pdfjs-dist:2.0.489