Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RelatedEntries is not loaded after migrating from mix to vite #1400

Closed
AmooAti opened this issue Nov 1, 2023 · 0 comments · Fixed by #1401
Closed

RelatedEntries is not loaded after migrating from mix to vite #1400

AmooAti opened this issue Nov 1, 2023 · 0 comments · Fixed by #1401
Labels

Comments

@AmooAti
Copy link

AmooAti commented Nov 1, 2023

Telescope Version

4.17.0

Laravel Version

10.25.2

PHP Version

8.2.12

Database Driver & Version

10.6.12-MariaDB-0ubuntu0.22.04.1 - Ubuntu 22.04

Description

In this version, the related-entities view is not loaded, and there is an error in the browser console, which I think can't load loadash.

Screenshot from 2023-11-01 16-29-00

In the above screenshot, we should have queries and logs.

Steps To Reproduce

  1. Install Laravel Telescope on a Laravel application.
  2. Go with standard Installation and configuration.
  3. create a route that logs a message using Log facade.
  4. query a model, for example User::all()
  5. make a request.
  6. see the request details for related entities. Queries and Logs don't show up.
crynobone added a commit that referenced this issue Nov 1, 2023
@crynobone crynobone added the bug label Nov 1, 2023
taylorotwell pushed a commit that referenced this issue Nov 1, 2023
…1401)

* Fixes RelatedEntries is not loaded after migrating from mix to vite

fixes #1400

Signed-off-by: Mior Muhammad Zaki <[email protected]>

* Compile Assets

---------

Signed-off-by: Mior Muhammad Zaki <[email protected]>
Co-authored-by: crynobone <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants