level | tags |
---|---|
3 |
pinia, state |
Lorem Ipsum?
Alpha
<?php | |
namespace Database\Seeders; | |
use Illuminate\Database\Seeder; | |
use Illuminate\Support\Facades\DB; | |
class MovieSeeder extends Seeder | |
{ | |
public function run() |
<?php | |
namespace Database\Seeders; | |
use App\Models\Course; | |
use PrismPHP\Prism\Prism; | |
use Illuminate\Database\Seeder; | |
use Illuminate\Support\Facades\File; | |
use Prism\Prism\Schema\ArraySchema; | |
use Prism\Prism\Schema\NumberSchema; |
One of the things that mildly annoys me after installing Laravel is dealing with migrations I'll never use—or worse, accidentally running them.
What do I mean? Well, when you create a new Laravel project using the installer, you get three migrations by default:
import { defineConfig } from 'vite'; | |
import jigsaw from '@tighten/jigsaw-vite-plugin'; | |
export default defineConfig({ | |
plugins: [ | |
jigsaw({ | |
input: ['source/_assets/js/main.js', 'source/_assets/css/main.css'], | |
refresh: true, | |
}), | |
], |
yarn run v1.22.21 | |
warning package.json: No license field | |
$ nuxi dev | |
Nuxt 2.18.1 with Nitro 2.10.4 nuxi 3:07:31 PM | |
3:07:31 PM | |
➜ Local: http://localhost:3000/ | |
➜ Network: use --host to expose | |
ℹ Module nuxt-bridge took 11.64ms to setup. 3:07:33 PM |
<!DOCTYPE html> | |
<html lang="en"> | |
<head> | |
<meta charset="utf-8"> | |
<meta name="viewport" content="width=device-width, initial-scale=1"> | |
<title>Guess This Drawing!</title> | |
<script src="https://cdn.tailwindcss.com"></script> | |
<link href="https://fonts.googleapis.com/css2?family=Bowlby+One+SC&display=swap" rel="stylesheet"> | |
</head> |
Laravel Mix has been replaced by Vite in Jigsaw 1.8. New installations will use Vite by default when running jigsaw init
.
To upgrade an existing site, follow these steps:
# Upgrade to Jigsaw 1.8
composer require tightenco/jigsaw:^1.8 -W
# Remove Mix and Jigsaw Mix
npm remove laravel-mix laravel-mix-jigsaw
Auto Importing Components
Auto imports make refactoring much easier. If you change the name or location of a component—say, from Foo/HelloWorld
to Bar/GoodByeWorld
—auto imports save you from manually updating every import line across your codebase.
With auto import:
-<HelloWorld>
+<GoodByeWorld>