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

Problem when installing Livewire on Jetstream #61

Closed
AbeGNING opened this issue Sep 5, 2020 · 3 comments
Closed

Problem when installing Livewire on Jetstream #61

AbeGNING opened this issue Sep 5, 2020 · 3 comments

Comments

@AbeGNING
Copy link

AbeGNING commented Sep 5, 2020

  • Jetstream Version: 0.6.4
  • Laravel Version: 8.0
  • PHP Version: 7.4.9

Description:

I'm new to Jetstream, but I get the same error after trying to install it several times.

Steps To Reproduce:

  1. I installed Laravel 8 with laravel new project --dev.
  2. then Jetstream with composer require laravel/jetstream.
  3. Livewire installation: php artisan jetstream: install livewire
  4. Compiling the frontend assets: npm install && npm run dev
  5. I encounter the error when I do: php artisan serve or php artisan vendor: publish --tag = jetstream-views

Capture

@calebporzio
Copy link
Contributor

Hi @AbeGNING,

I was unable to reproduce your error. I followed the steps exactly and everything worked perfectly for me.

My best guess as to what is going on:

  • The ::macro method was PR'd into that class 2 months ago (to 7.x AND master (8.x)): [7.x] Make ComponentAttributeBag Macroable framework#33354
  • Therefore, my only guess is that you are using a version of Laravel before that PR made it in. This is odd because you explicitly newed up a Laravel app with `--dev.

One thing you could try is running: composer global update "laravel/installer:^4.0" (If that doesn't work, manually bump your ~/.composer/composer.json file's laravel/installer version to "^4.0").

Hope one of these things helps!

@edgrosvenor
Copy link

--dev was giving me an old version of Laravel last night too. So this might be composer's fault somehow. I don't know enough about its inner workings to assign blame, but I definitely witnessed some misbehavior.

@imClement
Copy link
Contributor

I was experiencing the exact same problems.
composer global update "laravel/installer:^4.0" did not fix it as the installer was not updated on 4.0

but

manually bumping the ~/.composer/composer.json file's laravel/installer version to "^4.0", followed by installer update, fixed the problems.

Thank you.

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

5 participants