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

docs: add debugging section #6857

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,85 @@
---
title: Debugging | Qwik City
description: Qwik apps can be sometimes tricky to debug, here are some tips and tricks to help you out.
contributors:
- czuma
- maiieul
- thejackshelton

updated_at: '2024-08-03T00:00:01Z'
created_at: '2024-08-03T00:00:01Z'
---

import PackageManagerTabs from '~/components/package-manager-tabs/index.tsx';

# Debugging Qwik

Debugging web applications can be a challenge, but fear not! This guide will provide you with some helpful tips and tricks to help you debug your Qwik application.

## Debug Big JS Chunks

Sometimes you might notice when you build your application or preview it, Vite and Rollup will output a notice complaining about large chunks of code being generated.

```
(!) Some chunks are larger than 500 kB after minification. Consider:
- Using dynamic import() to code-split the application
- Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks
- Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
```

In simple terms, something you import or use in your project is probably way too big, and is not been split into smaller chunks.
And will outperform when you send it to the client.

First you will notice is that the chunk names are not very helpful to identify the plug-in or library or file that is causing the issue.

Because it's minified.
[![Rollup complaining](rollupcomplain.png)]


### rollup-plugin-visualizer

This plugin is a tool that will help you visualize the size of your chunks in a very simple html file.
First Install the plugin:

<PackageManagerTabs>
<span q:slot="pnpm">
```shell
pnpm add -D rollup-plugin-visualizer
```
</span>
<span q:slot="npm">
```shell
npm install --save-dev rollup-plugin-visualizer
```
</span>
<span q:slot="yarn">
```shell
yarn add --dev rollup-plugin-visualizer
```
</span>
</PackageManagerTabs>

Second, edit your `vite.config.ts` file to include the plugin:

```ts
// Import the plugin and types
import { type PluginOption } from 'vite'
import { visualizer } from "rollup-plugin-visualizer";

// Add the plugin to the plugins array
plugins: [
...
visualizer() as PluginOption
]

```

Third, run your build or preview the same way you normally do.

This will create a new file in the root of your project called `stats.html` that you can open in your browser.

The file will contain a visualization of the size of your chunks, and you can see which file is causing the issue.

[![The Big Chunk](locatebigchunk.png)]

In the example above, we can see that `faker` library is causing the issue.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.