home.social

#biomejs — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #biomejs, aggregated by home.social.

fetched live
  1. Tried again to switch from prettier to #BiomeJS (@biomejs) on work projects.

    Good news is that formatting #Typescript works well and prettier compatibility is now near perfect.

    Bad news are that it doesn't yet format sass or yaml, the VSCode extension is invasive and configuration file is still horrible.

    🤷‍♂️ will try again in 6 months

  2. Tried again to switch from prettier to #BiomeJS (@biomejs) on work projects.

    Good news is that formatting #Typescript works well and prettier compatibility is now near perfect.

    Bad news are that it doesn't yet format sass or yaml, the VSCode extension is invasive and configuration file is still horrible.

    🤷‍♂️ will try again in 6 months

  3. Why bother with the Sisyphean task of migrating from Prettier and ESLint to #BiomeJS when you can just use a 🪓 to #refactor your entire codebase? It's like trading your bicycle for a tricycle and expecting to win the Tour de France. 🚴‍♂️💨
    blog.appsignal.com/2025/05/07/ #SisypheanTask #Codebase #DeveloperHumor #CodingChallenges #HackerNews #ngated

  4. Why bother with the Sisyphean task of migrating from Prettier and ESLint to #BiomeJS when you can just use a 🪓 to #refactor your entire codebase? It's like trading your bicycle for a tricycle and expecting to win the Tour de France. 🚴‍♂️💨
    blog.appsignal.com/2025/05/07/ #SisypheanTask #Codebase #DeveloperHumor #CodingChallenges #HackerNews #ngated

  5. Looking for advice on how to refactor legacy #JavaScript #frontend code (My expertise is on backend).

    I know how to write relatively clean JS / #TypeScript for frontend in modern setups with modern tooling, but I'm not sure how to proceed with thousands-of-lines long files that are directly included as they are, so I can transition to having smaller & cleaner files and using static analysis tools that give me some peace of mind.

    My only achievement so far with my current project is that I run #BiomeJS on some selected files.

    I'm relying on #JSDoc for now, but "for my eyes only", I'm not using this typing information to validate anything.

    #refactoring #legacycode

  6. Looking for advice on how to refactor legacy #JavaScript #frontend code (My expertise is on backend).

    I know how to write relatively clean JS / #TypeScript for frontend in modern setups with modern tooling, but I'm not sure how to proceed with thousands-of-lines long files that are directly included as they are, so I can transition to having smaller & cleaner files and using static analysis tools that give me some peace of mind.

    My only achievement so far with my current project is that I run #BiomeJS on some selected files.

    I'm relying on #JSDoc for now, but "for my eyes only", I'm not using this typing information to validate anything.

    #refactoring #legacycode