660 experience to go until the next level!
In case you were wondering, you earn Laracasts experience when you:
Earned once you have completed your first Laracasts lesson.
Earned once you have earned your first 1000 experience points.
Earned when you have been with Laracasts for 1 year.
Earned when you have been with Laracasts for 2 years.
Earned when you have been with Laracasts for 3 years.
Earned when you have been with Laracasts for 4 years.
Earned when you have been with Laracasts for 5 years.
Earned when at least one Laracasts series has been fully completed.
Earned after your first post on the Laracasts forum.
Earned once 100 Laracasts lessons have been completed.
Earned once you receive your first "Best Reply" award on the Laracasts forum.
Earned if you are a paying Laracasts subscriber.
Earned if you have a lifetime subscription to Laracasts.
Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.
Earned once you have achieved 500 forum replies.
Earned once your experience points passes 100,000.
Earned once your experience points hits 10,000.
Earned once 1000 Laracasts lessons have been completed.
Earned once your "Best Reply" award count is 100 or more.
Earned once your experience points passes 1 million.
Earned once your experience points ranks in the top 50 of all Laracasts users.
Earned once your experience points ranks in the top 10 of all Laracasts users.
Started a new Conversation Mix Notifications Under Windows 10 WSL
I'm running Ubuntu 20 under WSL and it works great. One thing missing is the compile notifications. I have a bash script working that calls a PowerShell thingy called BurntToast.
~/STGdev $ wsl-notify "Compile was Successful"
Is there any way to connect this to the npm run dev or watch mix config?
Thanks, Jim in Florida
Started a new Conversation L7 Vuetify SPA Into L8, Jet, Fortify, Interia
I have a L7 app in development that uses Vuetify SPA with vue-router setup and working. Currently I have login and register auth working via axios into the L7 api.php endpoint and it works OK. I don't have ForgotPassword and EmailVerification working.
I'm willing to dump that auth and go with L8, Jet, Fortify, Inertia --- I want auth to be done with and to move on---BUT, will I have to move all our current Vue/Vuetify under Interia?
Is this a month long rabbit hole? Will they need to take me away in a straight jacket?
Started a new Conversation L8, Jet, Inertia: Looking For App In The DOM
OK, trying to move our Vuetify app to L8, Jet, inertia. I see this line in // resources/js/app.js
const app = document.getElementById('app');
It's grabbing the app element in the DOM. My question is --- what defined the app.
In my L7 app, it's defined in the single blade.php
<!-- Styles -->
<link href="{{ asset('css/app.css') }}" rel="stylesheet">
</head>
<body>
<div id="app"></div>
<script src="{{ asset('js/app.js') }}" defer></script>
</body>
I can't find it in L8 and this gets this....
initialPage: JSON.parse(app.dataset.page),
[Vue warn]: Error in render: "SyntaxError: Unexpected token u in JSON at position 0"
Thanks, Jim in Florida
Replied to L7 Vuetify App Move To L8
OK, I looked those Jetstream routes and I see pretty much everything except /login and /register, but I guess I don't need to worry about it as I didn't worry about Auth::routes(); in L7.
Do you think I can get Vuetify to coexist with L8, Jetstream, intertia and Tailwind?
Started a new Conversation L7 Vuetify App Move To L8
We use a Vuetify tree as an important part of our SPA app. All Auth is done via axios into the api.php route. What are my success rate chances on moving the app into the L8, Jetstream, intertia stack? I'm willing and interested to dump my current "homemade" auth and using the L8 'outta-the-box' solution.
And, why am I able to add /login to http://localhost --- but I don't see /login as a route in web.php ??
Thanks, Jim in Florida
Replied to Nova Vs SPA
Do the front and backend have to be developed and run from the same directory?
Replied to Nova Vs SPA
Does this mean that I would have to use Nova thru an axios /api/ call from my SPA and write my own UX/UI ?
Replied to Nova Vs SPA
But if I use http://myvueapp.com/login -- vue router will let me log in.
But if I use http://myvueapp.com/nova -- I will 404 because Nova is not installed here, it's over on the backend !?!
Do I understand this correctly?
Started a new Conversation Nova Vs SPA
OK, given a Vue SPA project with vue-router in it's own directory, say /front and a Laravel project in it's own directory, say /back
I understand how Vue can route to login.vue and register.vue and say, products.vue and how they can axios to the /routes/api.php router.
But, they seem so separate and independent. We want Nova available to our developers and admin folks and a given subset of Nova available to customer team administrators. With Nova installed on the /back, it won't be available via the Vue router in the /front, so... Nova is more important to us than the SPA, so I guess I have to ditch the SPA idea......true?
Replied to Setting Up A Laravel Dev Machine On Windows 10 With WSL (Windows Subsystem For Linux) Enabled
Yes, VS Code !! When I open a Bash shell in Ubuntu 20 WSL2 and enter
$ code .
The WSL folks include in the Linux path: /mnt/c/Program Files/Microsoft VS Code/bin
So vscode runs and on the first run it automatically enables it's Remote-WSL mode! VS Code stays actually running under windows but seamlessly remotes into WSL where the files are stored and run. I'm using Windows Terminal Preview 1.2.2 and using Bash into WSL and I configured the terminal inside of vscode to run the same!
All works just great!
Started a new Conversation TypeError: Text.forEach Is Not A Function
This just started happening ...
~/STGdev/lvvn $ npm run watch
> @ watch /home/gymdo/STGdev/lvvn
> npm run development -- --watch
> @ development /home/gymdo/STGdev/lvvn
> cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js "--watch"
10% building 1/1 modules 0 active
webpack is watching the files…
98% after emitting SizeLimitsPlugin
ERROR Failed to compile with 1 errors 10:22:54 PM
error in ./resources/sass/app.scss
Module build failed (from ./node_modules/css-loader/dist/cjs.js):
TypeError: text.forEach is not a function
at /home/gymdo/STGdev/lvvn/node_modules/extract-text-webpack-plugin/dist/loader.js:145:16
I've spent 10 hours trying to fix it ... searching and trying things .... This error happens when my webpack.mix.js is the original installation.
Looks the same as this ... https://www.bountysource.com/issues/92161278-unexpectedly-fails-with-css-loader-v4-0-0