Hugging Face's logo

Spaces:
soiz1
/
eruda-vue
Build error

App Files Community
eruda-vue
File size: 2,894 Bytes 
4d70170
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
 
# Profiling devtools performance

If you experience performance issues while using the devtools, this guide will explain how to profile the devtools and share the result to the team.

## 1. Setup environment

First you need to clone and setup the devtools repository as [explained in the contributing guide](./contributing.md#development).

## 2. Run Chrome with web security disabled

The development shell for the devtools is a page with a development version of the devtools and an iframe mimicking the page being inspected.

Normally inspecting the iframe would only work on the same domain (here `localhost`), but we can workaround this limitation by disabling web security in Chrome.

```bash
/path/to/chrome --disable-web-security --disable-site-isolation-trials --user-data-dir="temp-chrome-data"
```

::: danger
Do not browse to any other website while using this Chrome instance, as it will disable some security features.
:::

## 3. Open dev shell

Make sure you have run both the `build:watch` and the `dev:vue3` scripts as [explained in the contributing guide](./contributing.md#development).

In the Chrome window, open the devtools development shell at `http://localhost:8090`.

You can then change the target URL in the toolbar on top of the devtools:

![devtools shell screenshot](../assets/dev-shell-url.png)

## 4. Create a profiling session

Open the Chrome devtools and go to the Performance tab.

Start a performance recording by clicking the record button:

![start a profile screenshot](../assets/dev-shell-profile-start.png)

Then try to reproduce the performance issues by using your application and the devtools for 10 or 20 seconds.

## 5. Export the profiling data

When your are done, stop the recording by clicking the stop button:

![stop a profile screenshot](../assets/dev-shell-profile-stop.png)

Then click the "Save profile..." button to export the profiling data:

![export a profile screenshot](../assets/dev-shell-profile-export.png)

## 6. Share the profiling data

Check your Vue devtools version number in the Extensions tab of Chrome:

![devtools version screenshot](../assets/devtools-version.png)

Post a new comment [here](https://github.com/vuejs/devtools/discussions/1968) with the following information:

- Run `npx envinfo --system --browsers` and paste the result. Make sure is contains your OS version and Chrome version.
- Vue Devtools version.
- Upadload the profiling data file in the comment (you can drag and drop it in the comment box).

Example:

```
  System:
    OS: Linux 5.19 Fedora Linux 36 (Workstation Edition)
    CPU: (24) x64 AMD Ryzen 9 3900XT 12-Core Processor
    Memory: 34.66 GB / 62.71 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Browsers:
    Chrome: 106.0.5249.103
    Firefox: 105.0.1

  Vue Devtools version: 6.4.3

  (Don't forget to upload the profile data file!)
```

Thank you for your contribution!