bun icon indicating copy to clipboard operation
bun copied to clipboard

This package works in node but not with bun.

Open rktmatt opened this issue 10 months ago • 1 comments

What version of Bun is running?

No response

What platform is your computer?

No response

What steps can reproduce the bug?

This is a reference to this issue : https://github.com/nuxt-modules/supabase/issues/266

I've seen in Bun 1.1 video to report to Bun things that work in node but not in Bun.

Thanks !

What is the expected behavior?

No response

What do you see instead?

No response

Additional information

No response

rktmatt avatar Apr 04 '24 18:04 rktmatt

I'm having the same issue.

anthonyfranc avatar Apr 05 '24 11:04 anthonyfranc

Duplicate of #9948

Electroid avatar Apr 09 '24 00:04 Electroid

Duplicate of #9948

that's not a duplicate of #9948. The bug in #9948 was something that worked in 1.0 (I used that command successfully) and it doesn't work in 1.1 apparently (I haven't tested 1.1 because Bun just doesn't work properly on my framework)

But okay, keep both closed if you're already giving up in what you say in a video just a week ago or so. Well I don't see why we should bother using Bun at all.

rktmatt avatar Apr 09 '24 12:04 rktmatt

Duplicate of #9948

that's not a duplicate of #9948. The bug in #9948 was something that worked in 1.0 (I used that command successfully) and it doesn't work in 1.1 apparently (I haven't tested 1.1 because Bun just doesn't work properly on my framework)

But okay, keep both closed if you're already giving up in what you say in a video just a week ago or so. Well I don't see why we should bother using Bun at all.

Is there another issue that you're seeing? When I reproduced this issue, I ran into that error with Bun 1.1, which is why I marked it as a duplicate.

Electroid avatar Apr 09 '24 17:04 Electroid

Duplicate of #9948

that's not a duplicate of #9948. The bug in #9948 was something that worked in 1.0 (I used that command successfully) and it doesn't work in 1.1 apparently (I haven't tested 1.1 because Bun just doesn't work properly on my framework) But okay, keep both closed if you're already giving up in what you say in a video just a week ago or so. Well I don't see why we should bother using Bun at all.

Is there another issue that you're seeing? When I reproduced this issue, I ran into that error with Bun 1.1, which is why I marked it as a duplicate.

thank you for getting back on this.

You ran into the issue during installation, for the package manager part of bunx in 1.1 that apparently do not work.

The issue I linked was during bunx runtime not during install. Bun runtime did work for nuxt before but it didn’t work if Supabase module for Nuxt was intalled, that’s why there was a ticket over there previously.

rktmatt avatar Apr 09 '24 18:04 rktmatt

Duplicate of #9948

that's not a duplicate of #9948. The bug in #9948 was something that worked in 1.0 (I used that command successfully) and it doesn't work in 1.1 apparently (I haven't tested 1.1 because Bun just doesn't work properly on my framework) But okay, keep both closed if you're already giving up in what you say in a video just a week ago or so. Well I don't see why we should bother using Bun at all.

Is there another issue that you're seeing? When I reproduced this issue, I ran into that error with Bun 1.1, which is why I marked it as a duplicate.

thank you for getting back on this.

You ran into the issue during installation, for the package manager part of bunx in 1.1 that apparently do not work.

The issue I linked was during bunx runtime not during install. Bun runtime did work for nuxt before but it didn’t work if Supabase module for Nuxt was intalled, that’s why there was a ticket over there previously.

Confirming this, I did a fresh install of nuxt once I added in supabase it fails.

anthonyfranc avatar Apr 09 '24 19:04 anthonyfranc