install from composer gives you something weird?

[baradhili]

running composer require --dev bfinlay/laravel-excel-seeder gave me "bfinlay/laravel-excel-seeder": "^1.2"

Is it that I need to put the repo in for this one?

[bfinlay]

If you type composer require --dev bfinlay/laravel-excel-seeder:^3.0 does it give you any error messages?

[baradhili]

works fine, but without the version then it installs 1.2

[bfinlay]

I missed your reply previously. Did you resolve this?

I suspect this is an issue with version constraints for your composer packages.

When I run composer require --dev bfinlay/laravel-excel-seeder on a composer.json that does not have bfinlay/laravel-excel-seeder, it initially updates composer.json with "bfinlay/laravel-excel-seeder": "*", then it automatically runs composer update, then it updates composer.json with the latest release version, v3.3.

What is the output of this command? composer depends bfinlay/laravel-excel-seeder

[bfinlay]

Closed for now. If there is more information feel free to add a comment.

[bfinlay]

In connection with issue #22, I updated the readme.md to recommend using the -W switch with composer require.

I also added a test to github actions that creates a laravel app and runs composer require for each laravel and php configuration. Currently this test runs composer require without the --dev switch because that was the scenario in #22. The test also specifies the version as "dev-master" because I want to run the test against the tip.

You can look at the github actions tests here: https://github.com/bfinlay/laravel-excel-seeder/actions

[bfinlay]

I may add a test in the future that runs composer require and verifies that the latest version is installed.