Laravel Config Cache Not Updating in VSCode Terminal

[bloodykheeng]

Laravel Version

11.0

PHP Version

8.2.12

Database Driver & Version

No response

Description

Laravel Config Cache Not Updating in VSCode Terminal

Description

I've encountered an issue where Laravel's mail configuration cache doesn't update properly when using the VSCode integrated terminal, but works correctly when using Windows Command Prompt or PowerShell opened through Windows Search.

Problem

When I modify mail configurations in my .env file and run the standard Laravel config cache commands in VSCode's integrated terminal:

php artisan config:clear
php artisan config:cache

The cache appears to clear (bootstrap/cache gets cleared), but when I run:

php artisan config:show mail

The old configurations are still showing - the new configs from my .env file are not being cached.

Workaround

The issue is resolved when I use Windows Command Prompt or PowerShell opened directly through Windows Search instead of VSCode's integrated terminal:

1. Open Command Prompt or PowerShell through Windows Search
2. Navigate to project directory
3. Run the same commands:

   php artisan config:clear
   php artisan config:cache

After running these commands in the external terminal, both VSCode terminal and the external terminal show the updated mail configurations when running php artisan config:show mail.

Environment

• OS: Windows
• Editor: Visual Studio Code
• Framework: Laravel
• Terminal: VSCode Integrated Terminal vs Windows CMD/PowerShell

Expected Behavior

Config cache commands should work consistently regardless of which terminal is used.

Actual Behavior

VSCode terminal fails to properly update the config cache with new environment variables, while external Windows terminals work correctly.

Possible Causes

This might be related to:

• Environment variable inheritance differences between VSCode terminal and system terminals
• File permission issues
• Path resolution differences
• VSCode terminal environment isolation

Impact

This issue can cause confusion during development and may lead to testing with incorrect configurations when using VSCode's integrated terminal.

Steps To Reproduce

Steps to Reproduce

1. Modify mail configuration in .env file
2. Run php artisan config:clear in VSCode terminal
3. Run php artisan config:cache in VSCode terminal
4. Run php artisan config:show mail - observe old configs still cached
5. Open Windows CMD/PowerShell externally
6. Run the same commands in external terminal
7. Run php artisan config:show mail in both terminals - observe configs now updated

[mr-kamlesh-pawar]

File: tests/Foundation/FoundationConfigCacheTest.php

Add this test case:

public function test_config_cache_updates_in_vscode_terminal()
{
    // Simulate .env change
    file_put_contents(base_path('.env'), 'MAIL_MAILER=log');

    // Clear and rebuild cache
    $this->artisan('config:clear');
    $this->artisan('config:cache');

    // Verify cache updates
    $this->assertEquals('log', config('mail.mailer'));  // This will FAIL (proves the bug)
}

[bloodykheeng]

@mr-kamlesh-pawar where should i add it and why should i add it cos when i check in bootsrap folder i see the cache still has old envs as long as i use the vscode terminal to clear cache

[mr-kamlesh-pawar]

@bloodykheeng
Restart VSCode completely - Sometimes the terminal environment needs a full restart

Use the command palette (Ctrl+Shift+P) and run "Reload Window"

Try the VSCode PowerShell terminal instead of the default one

Clear cache manually:

php artisan cache:clear
php artisan view:clear
rm bootstrap/cache/config.php
Add this to your test case to help debug:

public function test_config_cache_updates_in_vscode_terminal()
{
    // Debug current environment
    dd([
        'env_MAIL_MAILER' => env('MAIL_MAILER'),
        'config_mail_mailer' => config('mail.mailer'),
        'cached_config' => require base_path('bootstrap/cache/config.php')['mail']['mailer']
    ]);
}

The test case proposed earlier was meant to help reproduce the issue, but the root cause is likely VSCode's terminal environment isolation. The workaround of using an external terminal is valid until Microsoft fixes this in VSCode.

[crynobone]

Seems to be an issue with VSCode instead a bug in the framework/app.