-
Notifications
You must be signed in to change notification settings - Fork 90
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
@react_component directive not working? #28
Comments
+1 |
Well, it should be working, sadly you're not the first to say this, I don't know yet what's happening. Can you try to use this example project (I should link to it at readme) https://github.com/talyssonoc/react-laravel-example ? |
Just tried, no that example project is not working for me either. Running this on Homestead, though not sure why that would make a difference. |
Just looked through some of the source, looks like you are using Facades now? I changed a line in the sample project to |
@nrcook actually react-laravel always used facades, what |
maybe we need to compile specific version of V8 lib not the last one and not to older one like 1.3 what is the working version stable of v8 lib working on ubuntu ? |
Yeah right now you cannot have a deferred service provider and a blade directive as it doesnt know to load the service provider associated with the directive. Hopefully in future laravel versions it would be possible for that to work. For now, I personally have just set the deferred property to false to get it to work. |
Well, I didn't know that ! Gonna fix it later today (a PR would be good, too). Thanks, @TomCaserta ! |
@TomCaserta @nrcook @lgt can you try this instructions here and say me if it does work? #41 (comment) |
Laravel 5.1, React-laravel 0.9.1
Tried on a couple different Laravel apps, both 5.0.* and 5.1. Neither one seemed to render the @react_component directive. Is there a missing step for getting this up and running that's not in the Readme?
Thanks!
The text was updated successfully, but these errors were encountered: