Skip to content

Laravel+Octane: Erro nos assets do Vite #486

Closed

Description

@andrefelipe18

Usando o preset do laravel+octane o Vite não está carregando corretamente os assets

Activity

  1. fabriciojs commented on Nov 16, 2023

    @fabriciojs
    Member

    @andrefelipe18 por favor, caso tenha mais algum detalhe das descobertas que obteve com o pessoal no Slack, e quiser registrá-las aqui.

    Vou tentar reproduzir o seu caso e se necessário criar algum ajuste no preset ou ao menos documentamos aqui o melhor caminho a seguir para ter Vite + Octane juntos.

  2. fabriciojs commented on Jan 6, 2024

    @fabriciojs
    Member

    @dbpolito you did get a solution for this on Slack, right? Could we add a Documenation entry for that? That should suffice at this moment.

  3. dbpolito commented on Nov 12, 2026

    @dbpolito
    Member

    Fixed by #544 and released in 3.8.1, with all standalone binaries and SHA-256 files attached. The Laravel and Octane presets now preserve the project’s existing Vite configuration/plugins and pass only Docker host/port flags through the dev-server command. Validated against Laravel 12/Octane and Laravel 13, including Tailwind, fonts, and HMR.

    Upgrade with kool self-update. For an existing project whose config was already overwritten by an older preset, restore its original Vite config from version control or vite.config.js.bak.*, then use the updated service command. The release cannot reconstruct a previously overwritten config automatically.

    Keeping this issue closed as completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinghelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions