-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Issue with bun support #63
Comments
Update on the issue: I downloaded the extension repo and went digging around.
The closest thing they have is bun pm ls which only lists the locally installed packages. My idea for a solution (that will work for all) is to call the npm registry via their api and get the versions that way. |
I love your excitement and thanks for making the time to do the PR! But I wish you discussed it first before making the time to implement it.. We're refactoring this feature soon and I'll consider your solution. |
No problem! If anything was fun to figure out. Cant wait to see what you've got in store |
@Blaquewithaq Do you face any other issues with Linux via WSL? |
Yes, there is another problem I came across after doing this PR. The function getOutdatedPackages needs to be reworked because bun does NOT have the command: I did find an issue for the missing feature and it looks like it may be added in the future: |
Environment
Nuxt project info:
What went wrong?
When using bun as the default package manager, the commands still use npm as the default manager.
I'm running linux in WSL on windows. I dont have npm install, only bun.
I've checked the developer logs on vscode to find this:
How to reproduce it?
Create an environment with ONLY bun (NO NPM). And try to update dependencies or install modules via the Nuxtr extension.
The text was updated successfully, but these errors were encountered: