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.

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

npm-asset/sortablejs ^1.10 -> could not be found in any version #71

Open
jozefrebjak opened this issue Aug 7, 2022 · 1 comment
Open

Comments

@jozefrebjak
Copy link

composer require tatter/workflows
Info from https://repo.packagist.org: #StandWithUkraine
Using version ^4.1 for tatter/workflows
./composer.json has been updated
Running composer update tatter/workflows
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires tatter/workflows ^4.1 -> satisfiable by tatter/workflows[v4.1.0].
    - tatter/workflows v4.1.0 requires npm-asset/sortablejs ^1.10 -> could not be found in any version, there may be a typo in the package name.

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.
 - It's a private package and you forgot to add a custom repository to find it

Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require tatter/workflows:*" to figure out if any version is installable, or "composer require tatter/workflows:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.
@MGatner
Copy link
Contributor

MGatner commented Aug 8, 2022

You may have to add Asset Packagist to your Composer repos (https://asset-packagist.org/). I thought that the source composer.json would be enough, but maybe not?

Also just to note: version 5 of this library has a current RC. This is a huge refactor of the code, so if you're just getting started I wouldn't recommend using version 4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants