feat: remove --disable-component-update from default args

[hackardoX]

Similarly to mozilla#3298,
Quoting:

Summarizing the “why” here:
The --disable-component-update command-line flag does two things: it disables component updates (desired) but it also prevents any bundled components from being initialised (undesired).

Disable this flag grant more flexibility, and it can always be disabled via the web-ext run --arg option

@aklinker1 Could you please check this PR? I would like to propagate the change to your vite-plugin-web-extension

[hackardoX]

Someone in @wxt-dev can review this? 😄

[aklinker1]

@andrea11 What are "components" in this case? I checked out the original puppeteer PR and chrome bug, but neither gave any context

[hackardoX]

Hi @aklinker1,
The definition of components provided by chromium is:

A component is any element of Chrome's core functionality that is sometimes delivered by the component updater separately from the browser itself, usually as a dynamically-linked library or data file.

In simpler words, components are pieces of chrome (chromium), that add some features or provides some data dynamically. For example, there is the "Autofill States Data" needed to make the chrome autofill working.
(By the way, the list of components can be accessed on chrome visiting the url chrome://components/)

Now, as mentioned in my first comments the --disable-component-update prevents any bundled components from being initialised.

[aklinker1]

Thanks for the explanation, that makes sense!

[aklinker1]

Ok so by removing the flag, we're saying that it's ok for the browser to install and initialize these components. Which makes sense for a non-testing/non-automated environment.

What does including the flag break for you?

[hackardoX]

@aklinker1 I was trying to create an extension using the vite-plugin-web-extension to play with the new (experimental) window.ai API. However, when I started the extension in the dev mode (npm run dev), vite uses web-ext-run to start the browser. Unfortunately, all components are disabled and this prevent me to make the window.ai works (it works fine on my browser when I use npm run build and then install as unpacked extension.
Do you think it is ok to merge this PR?

[aklinker1]

Yeah, I'll merge it. Just didn't understand the reasoning for it fully, but now I do. I'll merge and release later tonight, on my phone

[aklinker1]

Released in https://github.com/wxt-dev/web-ext-run/releases/tag/web-ext-run-v0.2.2