biome

> Oxfmt got it, and then won. This doesn't align with the data. - 650k npm downloads for oxfmt this week [0] - 4.3m npm downloads for biome this week [1] - 19.1k gh stars for oxfmt [2] - 23.7k gh stars for biome [3] - gap widening in favor of biome [4] [0] https://www.npmjs.com/package/oxfmt [1] https://www.npmjs.com/package/@biomejs/biome [2] https://github.com/oxc-project/oxc [3] https://github.com/biomejs/biome [4] https://www.star-history.com/#oxc-project/oxc&biomejs/biome&type=date&legend=top-left

Both of those have over >400 dependencies each [0] [1] but just in Rust instead - there hasn't been a Rust supply chain attack yet but is this any better? [2] Admittedly you're not normally downloading the dependencies to your machine as you're often using pre-built binaries, but a malicious package could still run if a version was shipped with it. [0]: https://github.com/biomejs/biome/blob/93182ea8e9d479fd0187ce... [1]: https://github.com/oxc-project/oxc/blob/65bd5584bfce0c7da90f... [2]: https://users.rust-lang.org/t/yet-another-npm-supply-chain-a...

Hi all, wow was not expecting this to be trending right now. I’m the creator of Boa, you can catch my talk about it at JS Conf EU 2019 https://www.youtube.com/watch?v=_uD2pijcSi4 That said, today Boa has a whole team of maintainers who I’m sure will answer some questions here. Yes the name does invoke the sense it’s a Python project but I liked it and stuck with it, I saw a Boa snake at a zoo once and knew I wanted to name my next project after it, I was also inspired by Mozilla at the time who named their projects after animals. Speaking of Mozilla, Boa’s existence came to be because at the time I was working on Servo and wanted to include an all-rust JS engine, one didn’t really exist so I set about making one as a learning exercise, after around 2 years more joined me on that journey and today Boa is around 8 years old. It is not brows

On the other hand, their actual dependency list looks closer to this, and this is definitely not comprehensive: https://github.com/ionic-team/capacitor https://github.com/Microsoft/tslib https://github.com/codemirror https://github.com/codemirror/autocomplete https://github.com/codemirror/language https://github.com/marijnh/style-mod https://github.com/marijnh/crelt https://github.com/marijnh/find-cluster-break https://github.com/marijnh/w3c-keyname https://github.com/cure53/DOMPurify https://github.com/electron/electron https://github.com/electron/get https://github.com/debug-js/debug https://github.com/vercel/ms https://github.com/sindresorhus/env-paths https://github.com/sindresorhus/got https://github.com/sindresorhus/is https://github.com/visionmedia/node-progress https://github.com/npm/node-semver https://github.com/malept/sumchecke

You usually can. You just gotta be a bit adventurous. https://github.com/lukeed/uvu is a testing library with almost no dependency. https://github.com/biomejs/biome is a linter written in Rust which in theory has a smaller attack surface. And as long as you stay some versions behind bleeding edge, you can use time in your favor to catch supply chain attacks before they reach your codebase.

When the left-pad debacle happened, one commenter here said of a well known npm maintainer something to the effect of that he's an "author of 600 npm packages, and 1200 lines of JavaScript". Not much has changed since then. The best counter-example I know is esbuild, which is a fully featured bundler/minifier/etc that has zero external dependencies except for the Go stdlib + one package maintained by the Go project itself: https://www.npmjs.com/package/esbuild?activeTab=dependencies https://github.com/evanw/esbuild/blob/755da31752d759f1ea70b8... Other "next generation" projects are trading one problematic ecosystem for another. When you study dependency chains of e.g. biomejs and swc, it looks pretty good: https://www.npmjs.com/package/@biomejs/biome/v/latest?active... https://www.npmjs.com/package/@swc/types?activeTab=dependenc... Replac

> is this the beginning of a larger trend where JS/TS tooling migrates to native implementations No, it is not. It is a continuation of an existing trend You may be interested in esbuild (https://github.com/evanw/esbuild), turborepo (https://github.com/vercel/turborepo), biome-js (https://github.com/biomejs/biome) are all native reimplementations of existing projects in JS/TS. esbuild is written in Go, the others in Rust. > reveals something deeper: Microsoft prioritized shipping a working solution over language politics Its not that "deep". I don't see the politics either way, there are clearly successful projects using both Go and Rust. The only people who see "politics" are those who see people disagreeing, are unable to understand the substance of the disagreement and decide "ah, it's just politics".

Note that Biome https://github.com/biomejs/biome is alive and well.

I had my doubts, but Tailwind's mantra "looks horrible, but you need to try it!" turned out to be true for me. You can think of Tailwind as the "APL of CSS." A single utility class can generate a lot of CSS for you, which is one advantage. The key benefit of Tailwind is that it co-locates your CSS with your HTML, reducing cascading issues and improving maintainability. Like any codebase, you can use your tools to add more structure and meaning. For example, I like using a tw function like this: export const tw = (...classes: (string | undefined | boolean)[]) => classes.filter(Boolean).join(" "); Using the tw function, your example classes would look something like this: class={tw( "fixed top-5 right-5 w-full max-w-xs p-4", "flex items-center space-x-4 divide-x divide-gray-200 rtl:divide-x-reverse dark:divide-gray-700"

I've started using https://biomejs.dev/ which is written in Rust. It's super fast compared to ESLint and doesn't require a ton of plugins to work (you just install the one @biomejs/biome package and that's it). The configuration is dead simple as well and it has VS Code and intelliJ support too. It also does formatting / prettifying in the same package as well. One downside though is it does not have support for Standard JS. They go by their own rules, which is fine for a new project, but existing projects that use Standard JS or have custom rules will probably take time to convert over, and not all ESLint rules are supported either. https://github.com/biomejs/biome/discussions/2070#discussion...

I am also confused by this goal, I've started a discussion in the repo to get some clarity on intent and direction there: https://github.com/biomejs/biome/discussions/1642

For TypeScript specifically there is some justification in that the TypeScript compiler is rather slow, so any speed benefits of Biome would go away if it relied on TypeScript for type information. But as a whole, not-invented-here syndrome has plagued Biome/Rome for the entire lifespan of the project. Like take a look at their error reporting code[1]. They made their own markup abstraction with their own Display trait and Write trait and a proc macro on top of it. It's cool code and probably does produce very nice error messages, but they could have easily used off the shelf crates like miette or ariadne and moved on to more important tasks. Or even their JS parser. It's a really nice JS parser! Maybe the best in terms of error reporting and AST resolution. But they could have easily used swc and maybe shipped the actual end-user product

Biome [0], a fast Prettier-compatible formatter, is currently working on adding class sorting [1]. We expect to ship the feature with the next release (on February). We are discussing which options to provide for the feature (mainly on the Discord of Biome). [0] https://biomejs.dev/ [1] https://github.com/biomejs/biome/pull/1362

A contributor is currently working on this feature [0] We are currently discussing which options to add to the rule on the Discord of Biome. We expect to ship the feature with the next release (on February). A nightly will be released earlier to gather feedback. [0] https://github.com/biomejs/biome/pull/1362