htmlparser2 VS mojo.js

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.

Have you looked at https://mobx-keystone.js.org/ by any chance?

I've been quite enjoying keystone + lit (or react if required) of late and at the very least it feels like solid prior art towards MVC stuff.

Also https://mojojs.org/ for server side.

(I'm not saying "use these" even if I quite enjoy using them myself, but they're my reference points for comparison here)

Mojo.js

A final interesting note is that the Mojolicious developer has also recently(-ish) created Mojo.js, which is Mojolicious implemented in Typescript.

mojo.js, it's a very old school web framework.

Express middleware support is on the planned feature list for 2.0 and beyond. Could also be implemented as a 3rd party plugin using the existing hook API though. https://github.com/mojolicious/mojo.js/issues/66

Just in case you missed it, Mojolicious is also available for TypeScript now, and the developer experience is pretty close to the Perl original. ;) https://mojojs.org

Aside from NestJS there is also mojo.js still innovating on the old MVC formula with TypeScript.