htmlparser2 VS Favifetch

I hear you! I went all-in to jQuery- scene. Even wrote a semi-famous library called "jQuery Tools" (oldies know). Then came React and I wrote Riot to simplify the syntax. Then I sidetracked to a startup world for (too) many years and watched aside how the frontend ecosystem grew to it's current dimensions.

Node uses a single dependency, htmlparser2 [1], in the package.json [2]. The HTML parser is used to traverse the HTML that is written on the Nue files. I quickly _thought_ of writing my own parser, but right now I'm having my eyes staring at Bun's native HTML parsing capabilities. Instead of Node, I'm using Bun to develop everything. I need less dependencies with it, because things like JS minification or .env file parsing are biult in.

[1]: https://github.com/fb55/htmlparser2

131 packages are looking for funding run `npm fund` for details 72 vulnerabilities (12 low, 19 moderate, 37 high, 4 critical) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. C:\Users\39388\Desktop\VALU PROCESS\FRONT\ConsultingBag_Frontend-main\ConsultingBag_Frontend-main> C:\Users\39388\Desktop\VALU PROCESS\FRONT\ConsultingBag_Frontend-main\ConsultingBag_Frontend-main>npm fund [email protected] ├─┬ https://opencollective.com/bootstrap │ │ └── [email protected] │ └── https://opencollective.com/popperjs │ └── u/popperjs/[email protected] ├── https://opencollective.com/date-fns │ └── [email protected] ├── https://opencollective.com/formik │ └── [email protected] ├── https://opencollective.com/styled-components │ └── [email protected] ├── https://github.com/sponsors/jacobwgillespie │ └── [email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected], u/styled-icons/[email protected] ├─┬ https://github.com/chalk/chalk?sponsor=1 │ │ └── [email protected] │ └── https://github.com/chalk/ansi-styles?sponsor=1 │ └── [email protected], [email protected] ├── https://github.com/sponsors/RubenVerborgh │ └── [email protected] ├── https://github.com/chalk/wrap-ansi?sponsor=1 │ └── [email protected] ├── https://opencollective.com/core-js │ └── [email protected], [email protected] ├─┬ https://opencollective.com/babel │ │ └── u/babel/[email protected] │ └── https://opencollective.com/browserslist │ └── [email protected], [email protected], [email protected] ├── https://github.com/sponsors/ljharb │ └── [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected] ├─┬ https://github.com/inikulin/parse5?sponsor=1 │ │ └── [email protected] │ └── https://github.com/fb55/entities?sponsor=1 │ └── [email protected], [email protected] ├── https://github.com/sponsors/fb55 │ └── [email protected], [email protected], [email protected], [email protected] ├── https://github.com/sponsors/sindresorhus │ └── [email protected], [email protected] ├── https://github.com/sponsors/epoberezkin │ └── [email protected] ├── https://github.com/sponsors/isaacs │ └── [email protected] ├── https://github.com/fb55/htmlparser2?sponsor=1 │ └── [email protected] ├── https://opencollective.com/postcss/ │ └── [email protected], [email protected] ├── https://github.com/sponsors/wooorm │ └── [email protected] ├── https://tidelift.com/funding/github/npm/autoprefixer │ └── [email protected] ├── https://github.com/sponsors/feross │ └── [email protected], [email protected], [email protected] ├─┬ https://paulmillr.com/funding/ │ │ └── [email protected] │ └── https://github.com/sponsors/jonschlinkert │ └── [email protected] └── https://tidelift.com/funding/github/npm/loglevel └── [email protected]

Why not just modify your code to use something more lightweight such as or something similar, and integrate your SvelteKit app with Cloudflare Workers using the official adapter? I’m pretty sure if configured correctly you could use their HTMLRewriter API.

I’ve created a favicon fetcher API using a vanilla Worker [link], although it’s not exactly what you’re doing and doesn’t use KV storage, it shows at least a little of what you’re trying to do