chore: feature gate html manipulation code

[Legend-Master]

Some initial effort on reducing the compile time, reference: #13382

This will be a breaking change in the tauri-utils crate, and we didn't mark this module as unstable before, so I'm not entirely sure if we can do this or should we wait for v3

[github-actions]

Package Changes Through 000ecb3

There are 7 changes which include tauri-bundler with patch, tauri with minor, @tauri-apps/api with minor, tauri-utils with minor, tauri-cli with patch, @tauri-apps/cli with patch, tauri-runtime-wry with patch

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package	current	next
@tauri-apps/api	2.5.0	2.6.0
tauri-utils	2.4.0	2.5.0
tauri-bundler	2.4.0	2.4.1
tauri-runtime	2.6.0	2.6.1
tauri-runtime-wry	2.6.0	2.6.1
tauri-codegen	2.2.0	2.2.1
tauri-macros	2.2.0	2.2.1
tauri-plugin	2.2.0	2.2.1
tauri-build	2.2.0	2.2.1
tauri	2.5.1	2.6.0
@tauri-apps/cli	2.5.0	2.5.1
tauri-cli	2.5.0	2.5.1

Add another change file through the GitHub UI by following this link.

---

Read about change files or the docs at github.com/jbolda/covector

[FabianLars]

we release breaking changes in tauri-utils all the time much to the dismay of users (and me cause i have to tell them to run cargo update lol) so why stop now

[Legend-Master]

Feel like we probably should just mark the entire crate unstable 🙃

[FabianLars]

well the problem is really how we consume it in tauri. if people update tauri they often do that in a way that doesn't update tauri-utils. We should really think about something like locking minor versions internally imho.

whether we mark it unstable or not, i don't care. most of the prior breaking changes could have been non-breaking as well if we'd change the api design a bit and/or use non_exhaustive more often.

[Legend-Master]

We should really think about something like locking minor versions internally imho.

Yeah, I'm also thinking about it, this is especially problematic for the plugins, we simplifies them to just 2 while we actually use some of features that requires a higher version

whether we mark it unstable or not, i don't care. most of the prior breaking changes could have been non-breaking as well if we'd change the api design a bit and/or use non_exhaustive more often.

To be fair, this crate is mostly for sharing code between the build script and the runtime crates, and probably can't be stable anyways

[FabianLars]

Yeah, I'm also thinking about it, this is especially problematic for the plugins, we simplifies them to just 2 while we actually use some of features that requires a higher version

I mean, the plugins are an easy fix. We can just set the minimum tauri versions they need. i thought that's what we were doing but just didn't had a reason already x)

To be fair, this crate is mostly for sharing code between the build script and the runtime crates, and probably can't be stable anyways

Maybe we shouldn't re-export it as-is from tauri then, but that's something for the next majors to worry about 🤷