-
If you search a package on bundlephobia you get the size of the entire package (see here). However, the entire react module doesn't get bundled and shipped to the client - only what you use does. That's why the npm module, using webpack, can get you more accurate sizes. If you look at import-cost.nvim, the front preview displays this fact: different import statements yield different code bundle sizes (although the npm module doesn't subtract duplicate bundled code). In the screenshot different react imports are different sizes. Not the most perfect analysis tool, but it just gives you insight about what you're using (for example, I didn't expect useFormik to be 9x bigger than useRef).
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
I actually tried using treesitter and bundlephobia in my first approach before defaulting to the npm module.
-
My own version of gruvbox-material. Highlights are done here in my dotfiles and the colorscheme itself is here
-
My own version of gruvbox-material. Highlights are done here in my dotfiles and the colorscheme itself is here
Related posts
-
Colorscheme doesn't properly work with NvimTree
-
Can someone help me configure Edge Light for my neovim?
-
Pain points with overriding colorscheme, specifically with CursorLineNr and Lualine
-
Vim not displaying listchars correctly for glyphs it can show in normal text
-
Procrastinated on real work while I added this hacky theme hot reload mechanism based on the hour of the day. What do y'all think?