v0.14.5 Fails with "no matching project for document" on standard nextjs/react project #1217
Assignees
Labels
bug
Something isn't working
Comments
thecrypticace
added a commit
that referenced
this issue
Feb 18, 2025
…" stylesheet (#1218) Fixes #1217 This issue kinda reveals that the entire detection around "project roots" or "root stylesheets" needs to be rethought because files at the top of a CSS graph may not actually be the intended stylesheet — especially when `@reference` is used. But… like anything… they also _might be_. In the meantime we'll "prefer" files we can detect as definite root stylesheets before trying other files.
|
This one is fun because it reveals a core assumption in how we detect projects is potentially wrong (… for some of them). 😅 I've merged a fix and am going to tag a release now and get one out in the next 15–30m or so. |
|
New release should be out (may take a bit for caches in VSCode to update). Sorry about that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Had to downgrade to v0.14.4 since the extension stopped working as soon as it got updated to v0.14.5. Project doesn't use any custom features, just basic NextJS/React with TS using Tailwind v4 configured using a basic
globals.cssfile. Noticed the issue when working on this branch: https://github.com/neploxaudit/neploxaudit.github.io/tree/article-listThe text was updated successfully, but these errors were encountered: