Skip to content
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

vscode extension cannot init in vscode v1.81.1 with unocss-extension 0.55.1 #2993

Closed
4 tasks done
zouhangwithsweet opened this issue Aug 17, 2023 · 11 comments · Fixed by #3005
Closed
4 tasks done

vscode extension cannot init in vscode v1.81.1 with unocss-extension 0.55.1 #2993

zouhangwithsweet opened this issue Aug 17, 2023 · 11 comments · Fixed by #3005
Labels

Comments

@zouhangwithsweet
Copy link
Contributor

UnoCSS version

0.55.1

Describe the bug

Cannot init.

Reproduction

版本: 1.81.1
提交: 6c3e3dba23e8fadc360aed75ce363ba185c49794
日期: 2023-08-09T22:20:33.924Z
Electron: 22.3.18
ElectronBuildId: 22689846
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Darwin x64 21.1.0

System Info

No response

Validations

@1oo1
Copy link

1oo1 commented Aug 17, 2023

+1. Resolved via rollback to 0.55.0.

1 similar comment
@LLLLevi-y
Copy link

+1. Resolved via rollback to 0.55.0.

@JianJia2018
Copy link

I have also encountered this issue. In version 0.55.1, it doesn't work within a VSCode project. I had to revert to the previous version.

@im-pan
Copy link

im-pan commented Aug 17, 2023

+1

1 similar comment
@xkli1220
Copy link

+1

@subframe7536
Copy link

same here

@loosheng
Copy link
Contributor

Related: #2979 #2992

@zaydek
Copy link

zaydek commented Aug 18, 2023

Oh I thought I was going crazy. Definitely rollback to 0.55.0 if you are having problems.

@sixdjango
Copy link

+1

@sixdjango
Copy link

you can "command + p" reload unocss , force reload

@zyyv zyyv added the vscode label Aug 19, 2023
@Jannchie
Copy link
Contributor

Jannchie commented Aug 19, 2023

I'm sorry for the disruption, it was my pr #2979 that introduced this issue...

I tried to commit #3005 to fix the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.