Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Package update failed: npm-asset/bootstrap-datepicker #68

Closed
schmunk42 opened this issue Sep 20, 2017 · 5 comments
Closed

Package update failed: npm-asset/bootstrap-datepicker #68

schmunk42 opened this issue Sep 20, 2017 · 5 comments
Assignees
@SilverFire
Labels
bug

Comments

@schmunk42
Copy link

I actually tried to install AdminLTE via npm

> composer require -vv --no-plugins npm-asset/admin-lte 
Using version dev-master for npm-asset/admin-lte
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Dependency resolution completed in 0.069 seconds
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for npm-asset/admin-lte dev-master -> satisfiable by npm-asset/admin-lte[dev-master].
    - npm-asset/admin-lte dev-master requires npm-asset/bootstrap-datepicker >=1.7.0,<2.0.0 -> no matching package found.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.

Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.

Installation failed, reverting ./composer.json to its original content.

So I looked up the missing package on ap: https://asset-packagist.org/package/search?query=bootstrap-datepicker&platform=bower%2Cnpm

But ap shows (https://asset-packagist.org/package/npm-asset/bootstrap-datepicker)

npm-asset/bootstrap-datepicker see on Npm
Fetch updates from Npm
Package update failed
Could you ensure this package exists on npmjs.com?

Think asset-packagist is guilty? Report on GitHub

And the package exists on npm, see https://www.npmjs.com/package/bootstrap-datepicker - I thought you're "guilty" ;)

PS: I would be really interested in the underlying issue here, since I fear a lot of problems coming up when using more and more npm packages. (see also yiisoft/yii2#14297)
@hiqsol hiqsol self-assigned this Sep 20, 2017
@hiqsol hiqsol added the bug label Sep 20, 2017
@SilverFire
Copy link
Member

SilverFire commented Sep 20, 2017 •
edited
Loading

It happens because one of bootstrap-datepicker releases contains invalid version constraint:

Failed to update package "npm-asset/bootstrap-datepicker": 
Could not parse version constraint >=1.1.0,,<2.0: Invalid version string "1.1.0,,<2.0"

@SilverFire
Copy link
Member

Same here: #25

@SilverFire SilverFire mentioned this issue Sep 20, 2017
Merged
@SilverFire
Copy link
Member

SilverFire commented Sep 20, 2017 •
edited
Loading

Create a PR to FXP: https://github.com/fxpio/composer-asset-plugin/pull/308/files

@SilverFire
Copy link
Member

PR merged, will deploy tomorrow

@SilverFire SilverFire assigned SilverFire and unassigned hiqsol Sep 27, 2017
@SilverFire
Copy link
Member

Deployed, package is available: https://asset-packagist.org/package/npm-asset/bootstrap-datepicker

@schmunk42 schmunk42 mentioned this issue Dec 19, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SilverFire SilverFire

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@schmunk42 @SilverFire @hiqsol