Skip to content

Merge Laravel Changes#1

Open
marky291 wants to merge 952 commits intomarky291:masterfrom
laravel:master
Open

Merge Laravel Changes#1
marky291 wants to merge 952 commits intomarky291:masterfrom
laravel:master

Conversation

@marky291
Copy link
Owner

@marky291 marky291 commented Sep 3, 2020

No description provided.

nunomaduro and others added 30 commits January 4, 2024 17:47
* Simplifies comments

* Apply fixes from StyleCI

* Removes non used line

* remove some comments

---------

Co-authored-by: StyleCI Bot <bot@styleci.io>
Co-authored-by: Taylor Otwell <taylor@laravel.com>
* update values for a sqlite default world

* migrate on post create project

* touch database

* fix typo
* Adjusts default mail environment variables

* Update .env.example

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>
* update example env for reverb

* remove broadcasting environment variables
nunomaduro and others added 30 commits October 20, 2025 17:30
* Replace Bootcamp with Laravel Learn

* Revise text for Laravel Learn section

Updated wording for Laravel Learn link in README.

* Update Laravel learning resources in README

Removed redundancy in Laravel learning resources and added a link to Laravel Learn for guided application building.

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>
* Add background driver

Adds settings for PR laravel/framework#57648

* Update queue.php

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>
* Ignore Laravel compiled views for Vite

Before testing, run php artisan cache:clear to clear old compiled views.

This issue only happens during local development when running npm run dev.
Laravel continuously recompiles Blade into PHP inside storage/framework/views (especially after Livewire re-renders), and these files are changed by Laravel itself, not by us.

Because of that, Vite thinks we modified a file and triggers a full reload—even though the change is purely internal framework logic. This makes the reload behavior unacceptable and noisy during development.

Since these compiled views belong to Laravel’s backend logic and not frontend assets, Vite does not need to watch them.

Ignoring storage/framework/views keeps Vite stable and prevents reloads caused by Laravel doing its own internal work.

* Vite ignore rule now in one clean line
```php
'pgsql' => [
   ...
    'sslmode' => env('DB_SSLMODE', 'prefer'),
]
```
* Update 0001_01_01_000001_create_cache_table.php

* Update 0001_01_01_000002_create_jobs_table.php

* Update 0001_01_01_000002_create_jobs_table.php

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>
Signed-off-by: Mior Muhammad Zaki <crynobone@gmail.com>
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

Successfully merging this pull request may close these issues.