Vite is a black box that can break at any time, I am starting to hate black boxes. Mix that in with flakey pnpm and node (we should all use deno now).

Good luck if something doesn't work in vite.

Proxy hasn't been working correct for me last 2 days so I ditched it and turned off chrome web security

Useless macos and app window selection

cmd + ` changes window in webstorm (clever them)

go to other app like chrome, cmd + ` does sfa

go to mac app settings and make cmd + ` work for all apps,

now go to webstorm and cmd + ` takes you out of webstorm if other apps open

i hate it

I'm sick of a toxic soup of ways to test frontend.

Throw in vitest, jest,jsdom, testing library, @testing-library/jest-dom, together and you are left with n^2 ways things can be configured.

Why on earth do I need to import anything to do with Jest when I am working with a vitest project.

I think such tools are made to get invite opportunities to speak at conferences.

I got tired of relearning JavaScript frameworks and instead tried to escape their clutches.

Most of my developer life I've spent relearning how to do the same thing in a different framework.

And every three or four years its the same story, figure out templating, figure out building, complain on github bugs etc.

I am trying to reduce framework fatigue by allowing you to think "can I make my application with just vanilla JavaScript". The advantage of vanilla JavaScript is it write once - do not need to rewrite.

Do YOU think I will abandon ship and end up having to use a framework again?