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
Describe the bug
A clear and concise description of what the bug is.
When running the supabase login command, the terminal freezes, well kinda... It disables in some way the ability to copy the link, and dosen't open it to my default browser. Basically like the "text selection" was disabled.
To Reproduce
Steps to reproduce the behavior:
Install the supabase cli on windows
Make sure you open a windows terminal (not cmd, could not test with that)
Install the cli as per the docs
Run supabase login
Press enter
You can't select the link and it's all broken
Expected behavior
The browser opening, or at least me being able to copy the link.
Screenshots
System information
Rerun the failing command with --create-ticket flag.
The feature didn't work, it ignored the flag when running the command.
Additional context
If applicable, add any other context about the problem here.
Default browser Arc for Windows
Version of supabase-js 1.178.2 (supabase --version)
Version of Node.js v20.9.0
Windows 11
The text was updated successfully, but these errors were encountered:
I mean either PowerShell or CMD, but in the windows Terminal app, which is default in win 11 and not the legacy window. And yes, I have and it didn't work.
Describe the bug
A clear and concise description of what the bug is.
When running the
supabase login
command, the terminal freezes, well kinda... It disables in some way the ability to copy the link, and dosen't open it to my default browser. Basically like the "text selection" was disabled.To Reproduce
Steps to reproduce the behavior:
supabase login
Expected behavior
The browser opening, or at least me being able to copy the link.
Screenshots
![image](https://private-user-images.githubusercontent.com/75439456/341995691-27c96b5c-ff75-40b0-b1f3-6682a0a22cf1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA1NzkwOTQsIm5iZiI6MTcyMDU3ODc5NCwicGF0aCI6Ii83NTQzOTQ1Ni8zNDE5OTU2OTEtMjdjOTZiNWMtZmY3NS00MGIwLWIxZjMtNjY4MmEwYTIyY2YxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzEwVDAyMzMxNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTU2Y2QwZTIxNTYzMjc5NDE2ZjZjN2MxNWUwZjg1ZGFmZGU5ZmFjMmU4YTBmMTAzYTgxNGRkMDZkYzM0NDNiZDYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.pLapWL7kEJwiLwo5ow9wxTF60zpzUBsOWQgVDU1hTw0)
System information
Rerun the failing command with
--create-ticket
flag.The feature didn't work, it ignored the flag when running the command.
Additional context
If applicable, add any other context about the problem here.
The text was updated successfully, but these errors were encountered: