vuex VS ESLint

Vuex is a state management library. At first glance it seems complicated, and in fact it is a bit. You can use Vuex to store data that should be used globally in your app. Vuex provides you with a solid API to apply changes to this data and reflect them in all child components that use Vuex data store.

I encourage you to also go through Vuex's official documentation: https://vuex.vuejs.org/

What makes Vue particularly powerful, however, is that it can be built upon, increasing its functionality from a simple view-model library to that of a fully fledged JavaScript framework capable of powering entire SPA's via supporting plugins and libraries such as Vue Router, Vue Resource, and Vuex.

Comparison, such as Pinia against Vuex, shows that Vuex, the previously recommended library, still has a higher download rate than Pinia. However, even the Vuex official documentation advises developers to opt-in for Pinia, since it is unlikely that Vuex will receive any additional functionalities.

Vuex a state management pattern + library for Vue.js release 4.0 - https://github.com/vuejs/vuex/releases/tag/v4.0.0

> poor support for style libraries like tailwind

Can't relate. Tailwind works fine with anything that supports PostCSS. I run it with Vite and there's zero issues.

> the state management ecosystem is fractured between vuex and pinia

This is also just not true. Pinia is officially replacing Vuex as the recommended store library for Vue [1]. They're also vastly similar in how they do things, so the knowledge transfer over from Vuex to Pinia. And Pinia just address most of the design goals mentioned in the article in the most simple way.

As for Vue 2 -> 3 transition, lots of the larger UI frameworks in the ecosystem is struggling to migrate, despite lots of efforts on the compat layer to smooth the transition, which is a bummer. But as long as you're not doing those sophisticated things, Vue 2 examples should work out-of-box on Vue 3 as well. There are surely less resources for the composition API, but the official introduction guide has been good enough in my experience.

[1]: https://vuex.vuejs.org/#what-is-vuex

Vue has a wide range of use cases that span the whole scale of front-end development. We can use it to add a bit of dynamism into an existing web app, such as adding a simple carousel or content that changes on user interaction e.g mouse movements or text input to creating complex web apps such as e-commerce stores with multiple categories and product pages supporting routing, browser-based data storage via Vue's own libraries such as the vue-router and vuex with features such as a cart, external API call requests and so forth.

replace global state managers like Redux or Vuex

Source: Vuex

When I arrived at the Vuex documentation page, I saw this:

Website: https://eslint.org/

ESLint is one of the most popular linters in the JavaScript community. It can help you catch bugs and enforce coding standards, which will make your code more readable and maintainable.

Just want to point out that using a linter like ESLint will highlight a lot of issues like this for you, even when writing React with JSX. It can be configured almost infinitely, but there are many great presets to get started (the defaults are pretty nice on their own).

I wish Google would invest more in go vet so it could do many of the things for which we currently rely on hobby-level tools that are rarely matured and often abandoned. ESLint, Clippy, and even clang-tidy show how much more comprehensive and mature lint suites can be, despite Go being easier to analyze than those languages.

Lints TypeScript code using ESLint.

The project is bootstrapped with Create React App and also includes eslint and prettier to ensure clean code.

ESLint is a tool that helps developers to identify and fix common coding errors and maintain consistency in their code. It provides a set of rules and guidelines that can be customized to fit the specific needs of a project. You can visit its official website to learn more: https://eslint.org/.

We have a style guide for Notion at our company, nothing super complicated but people invariably drift away from it. This is fine, we're just human. I'd ideally like to either automatically enforce certain styleguides or remind people to use them when they are not used in Notion. Basically I'm thinking of a linter/formatter you'd use when coding, like Prettier, eslint or LanguageTool.

Find and fix problems in your JavaScript code - ESLint - Pluggable JavaScript Linter