* chore: update deps as per npmx.dev recommendation

* fix: Add tinyglobby to replace omitted parts.

* fix: Add tinyglobby to replace omitted parts.

…on reload and HMR

Add a `liveReload` option to CrxOptions (default: true). When set to
false:

- The server skips sending crx:runtime-reload and crx:content-script-payload
- The service worker won't call chrome.runtime.reload() or relay HMR
  payloads to content scripts
- Content scripts won't call location.reload() on runtime reload events
- Files are still rebuilt and written to the output directory on change,
  so the user can manually reload the extension in Chrome

Closes #1146

Bumps [lodash](https://github.com/lodash/lodash) from 4.17.23 to 4.18.1.
- [Release notes](https://github.com/lodash/lodash/releases)
- [Commits](lodash/lodash@4.17.23...4.18.1)

---
updated-dependencies:
- dependency-name: lodash
  dependency-version: 4.18.1
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>

…18.1

chore(deps): bump lodash from 4.17.23 to 4.18.1

Vite virtual modules (e.g. plugin-vue:export-helper) produce filenames
containing colons via the /@id/ URL encoding. Colons are illegal in
Windows filenames, causing content scripts to fail to load during dev.

Add a sanitization step to getFileName() to replace colons with dashes.

Also add:
- Unit tests for getFileName() which previously had none
- E2e test asserting output filenames contain no Windows-illegal chars

fix: sanitize colons from output filenames on Windows

feat(vite-plugin): add liveReload option to disable automatic extension reload and HMR

Updated data_collection_permissions to be optional.

…issions

made data_collection_permissions optional

upgrade chokidar to lts

Version Packages