oruga VS stylelint

Have you looked at Oruga?

NaiveUI and DaisyUI are both pretty good. I'm currently migrating an app from Vue2 to Nuxt3 and used Oruga (I was using Buefy before) with Flowbite styles. It's a lot more work to get it working, though...

Oruga UI

Buefy is vue2 only.. what you might be looking for is Oruga

There is also Oruga, which is "minimal and yet functional." It is CSS framework agnostic, but has several plugins for different frameworks, such as Bootstrap, Tailwind and Bulma (or make your own CSS). It's pretty flexible.

Oruga UI (685 stars on GitHub) Oruga is a lightweight library of UI components without CSS framework dependency

Buefy will stay vue2, it's in maintenance mode as far as I know. The creator started a new framework for vue3, it's call Oruga and doesn't use any css framework.

You may be thinking of Buefy, which is Bulma+components packaged up for Vue2. Very nice framework, but it hasn't been updated for Vue3. Oruga is its spiritual successor and it supports Vue3.

Another common way to extend configs in linters is using the extends key in the configuration file. Let's take StyleLint as an example:

Stylelint is similar to ESLint, but its focus is on styling rather than JavaScript. It helps you find errors in style files, such as old syntax or empty classes. We will also incorporate stylelint-config-clean-order to sort your style rules and group them consistently across the entire codebase.

The “cost of loading modules” diagram shows non-linear behaviour (though you should largely ignore the curve visible in the diagram because the x axis is way off linear):

• 0.15s ÷ 500 = 0.3ms

• 0.31s ÷ 1000 = 0.31ms

• 3.12s ÷ 10000 = 0.312ms

• 16.81s ÷ 25000 = 0.6724ms

• 48.44s ÷ 50000 = 0.9688ms

My own observation on a Surface Book six years ago was that in Node.js under Windows, each module had about 1ms of overhead when there was warm file system cache—that is, simply bundling with Rollup saved 1ms per file. If this sort of thing interests you, quite a lot of useful stuff came out of https://github.com/stylelint/stylelint/issues/2454 which I filed because I was unhappy with stylelint taking over a second to import. And that must have been only in the order of one or two thousand modules, when the behaviour is still close enough to linear.

As the property is still experimental, stylelint does not recognize it yet at the time of writing this, so let's explicitly disable the property-no-unknown rule only where we use it by adding a stylelint-disable comment and re-enable it afterwards.

Document your build process in a blog, use eslint, stylelint and jsx-a11y lint. Run a lighthouse performance test, follow the optimisation reccomendations.

Run static analysis e.g. lint with lockfile-lint, Stylelint, ESLint, check for unimported files using unimported, and identify potential security vulnerabilities

Stylelint

I use StyleLint (https://stylelint.io/) to lint my css/scss. I don't think that's a rule, but writing a custom rule isn't too tough. And you can use the vscode extension - https://marketplace.visualstudio.com/items?itemName=stylelint.vscode-stylelint

The complete code for this project is in the Rodney Lab GitHub repo. I do hope the post has either helped you with an existing project or provided some inspiration for a new one. As an extension, you can add all your favourite future CSS rules to the PostCSS config. Beyond PostCSS for linting your input CSS, consider trying stylelint.