Livewire console error with version 2.17.10

I get this message with latest version. Downgrade to 2.17.8 is ok
22 Replies
Dan Harrin
Dan Harrin17mo ago
can you show us which line of code is missing this because wire-directives.js is a livewire core file
David Vincent
David Vincent17mo ago
How Dan ?
Dan Harrin
Dan Harrin17mo ago
can you not click on the stack trace?
David Vincent
David Vincent17mo ago
humm, sorry but I am lost. I just copied the console log that's it.
Dan Harrin
Dan Harrin17mo ago
yes but thats not helpful to us its a generic error and we cant see what line is causing it
David Vincent
David Vincent17mo ago
so what do you mean by "can you not click on the stack trace?" as I didn't click anywhere, just refreshing the page and displaying the console log.
Dan Harrin
Dan Harrin17mo ago
please open an issue then if you cant locate which line is causing the error :)
David Vincent
David Vincent17mo ago
David Vincent
David Vincent17mo ago
line 93
Dan Harrin
Dan Harrin17mo ago
thats not in the filament codebase though we're looking for a line of our code that causes the error
Dennis Koch
Dennis Koch17mo ago
Not sure why this is an issue at all. That line looks good
Dan Harrin
Dan Harrin17mo ago
yup
David Vincent
David Vincent17mo ago
and it's in the file livewire/livewire/js/util/wire-directives.js. This is very strange that I only have this issue if I upgrade to v2.17.10 and everything works fine with v2.17.8. I do filament:upgrade after every composer update, did a optimize:clear, clear browser cache. I understand that it's not part of filament, but very weird and I can't figure it out
Dennis Koch
Dennis Koch17mo ago
Did you only upgrade Filament or Livewire, too?
David Vincent
David Vincent17mo ago
livewire v2.12.2
Dennis Koch
Dennis Koch17mo ago
Yeah, but did the version change?
David Vincent
David Vincent17mo ago
yesterday, I downgrade to v2.12.0 and same issue
Dennis Koch
Dennis Koch17mo ago
Can you create a reproduction repo and an issue?
toeknee
toeknee17mo ago
@davidvincent_ch If you could let us know if you have solved it or provide a repo for us to reproduce it.
David Vincent
David Vincent17mo ago
I didn't solve it, I downgrade to 2.17.8
Dan Harrin
Dan Harrin17mo ago
unless you can give a reproduction repo, we cant fix this though?
David Vincent
David Vincent17mo ago
I found the origin, it's an issue with package awcodes/filament-quick-create, if I remove it, it works well. I don't know what's going on @awcodes