You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be a great improvement to also detect bun, a new and increasingly popular JavaScript runtime and package manager.
Specifically:
I noticed that oh-my-posh already supports bun as a CLI tool under the CLI segment.
Similarly, it would be helpful to add bun support in the Node segment by detecting the existence of bun.lockb (the lockfile used by bun projects).
Based on this detection, set .PackageManagerName to bun, and if possible, associate a .PackageManagerIcon just like npm, yarn, and pnpm.
This would ensure better compatibility with projects adopting bun and offer a more complete developer experience for users moving beyond traditional Node.js package managers.
The text was updated successfully, but these errors were encountered:
Code of Conduct
What would you like to see changed?
Currently, the Node segment's
PackageManagerName
only detectsnpm
,yarn
, andpnpm
whenfetch_package_manager
is enabled.https://ohmyposh.dev/docs/segments/languages/node#properties-1
It would be a great improvement to also detect
bun
, a new and increasingly popular JavaScript runtime and package manager.Specifically:
bun
as a CLI tool under the CLI segment.bun
support in the Node segment by detecting the existence ofbun.lockb
(the lockfile used by bun projects)..PackageManagerName
tobun
, and if possible, associate a.PackageManagerIcon
just like npm, yarn, and pnpm.This would ensure better compatibility with projects adopting
bun
and offer a more complete developer experience for users moving beyond traditional Node.js package managers.The text was updated successfully, but these errors were encountered: