[{"data":1,"prerenderedAt":26},["ShallowReactive",2],{"\u002Fblog\u002Ftags\u002Fnpm\u002F":3},[4,16],{"id":5,"path":6,"title":7,"description":8,"date":9,"readingTime":10,"tags":11},"blog_en\u002Fblog\u002F0006.lint-tailwind-css-v4-with-eslint.md","\u002Fblog\u002Flint-tailwind-css-v4-with-eslint","@angelblanco\u002Feslint-config 3.0 is out, now with Tailwind CSS","@angelblanco\u002Feslint-config 3.0 is available on npm: optional Tailwind CSS v4 linting, @antfu\u002Feslint-config v10 and ESLint 10.","2026-11-07","2",[12,13,14,15],"eslint","tailwindcss","tooling","npm",{"id":17,"path":18,"title":19,"description":20,"date":21,"readingTime":22,"tags":23},"blog_en\u002Fblog\u002F0003.create-your-eslint-config.md","\u002Fblog\u002Fcreate-your-eslint-config","Create your own ESLint config and share it across projects","If you've ever worked on multiple projects, you know the pain of copying ESLint configurations between repositories. Every time you set up a new project, you either start from scratch or copy the eslint.config.js file from your last one. There's a better way: publish your own shareable ESLint config package.","2025-11-02","3",[12,24,25,14,15],"typescript","vue",1794096651088]