lepikhinb / laravel-typescript

MIT License
391 stars 46 forks source link

Dependency issue when installing on Laravel 10 #29

Open LTroya opened 1 year ago

LTroya commented 1 year ago

Hi,

I am trying to install this package on a Laravel 10.13.5 project but it throws some dependency issues:

 Problem 1
    - based/laravel-typescript[v0.0.1, ..., v0.0.2] require illuminate/contracts ^8.37 -> found illuminate/contracts[v8.37.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
    - based/laravel-typescript v0.0.3 requires illuminate/contracts ^8.37|^9.0 -> found illuminate/contracts[v8.37.0, ..., v8.83.27, v9.0.0, ..., v9.52.9] but these were not loaded, likely because it conflicts with another require.
    - Root composer.json requires based/laravel-typescript * -> satisfiable by based/laravel-typescript[v0.0.1, v0.0.2, v0.0.3].

You can also try re-running composer require with an explicit version constraint, e.g. "composer require based/laravel-typescript:*" to figure out if any version is installable, or "composer require based/laravel-typescript:^2.1" if you know which you need.

Is there something I can do to install the package?

Current project dependencies:

"require": {
    "php": "^8.1",
    "guzzlehttp/guzzle": "^7.2",
    "inertiajs/inertia-laravel": "^0.6.8",
    "laravel/framework": "^10.0",
    "laravel/sanctum": "^3.2",
    "laravel/tinker": "^2.8",
    "tightenco/ziggy": "^1.0"
  },
  "require-dev": {
    "fakerphp/faker": "^1.9.1",
    "laravel/breeze": "^1.20",
    "laravel/pint": "^1.8",
    "laravel/sail": "^1.18",
    "mockery/mockery": "^1.4.4",
    "nunomaduro/collision": "^7.0",
    "pestphp/pest": "^2.0",
    "pestphp/pest-plugin-laravel": "^2.0",
    "spatie/laravel-ignition": "^2.0",
    "spatie/laravel-web-tinker": "^1.8"
  },

Kind regards.

nicoprocessor commented 1 year ago

@LTroya Check out this workaround, it worked for me on a brand new Laravel 10.14 installation: #25

Definitely not the best dev experience 😔

ltroya-as commented 1 year ago

@nicoprocessor you're right. Thanks for the workaround!