Dominik G.

if the disabled element does not emit mouse events, it won't get selected with a mouse https://github.com/sveltejs/vite-plugin-svelte/blob/339e8d399a922e677d3973063c8e2c62566b7e78/packages/vite-plugin-svelte-inspector/src/runtime/Inspector.svelte#L104 . esp firefox is known for not emitting events on disabled elements. however...

actually mouseover works, its the `click` to open the editor that does not. not sure how to work around that apart from creating a mask element thats layered on top...

you can add `input[disabled].svelte-inspector-active-target {pointer-events: none}` to the styles, but the behavior when moving the cursor over the element is a bit erratic then (toggling selection between parent and that...

switching from `click` to `pointerdown` would work. is that ok or do we need to wait for the corrosponding `pointerup` to see if it was "clickish" (short delta for time...

workaround is to press "Enter" while the disabled element is selected to open.

happy to add a json file providing metadata, renaming files would cause existing links to break and make it harder for humans to parse what they are looking for. if...

we also have one link self referencing it in a log https://github.com/sveltejs/vite-plugin-svelte/blob/ab2dd120e82edc39632d046bec3553e0da211285/packages/vite-plugin-svelte/src/utils/constants.js#L25

from your requirements it reads like get-tsconfig is a pretty good fit. What makes you consider tsconfck as a replacement? see https://github.com/dominikg/tsconfck/issues/31 and https://github.com/dominikg/tsconfck/discussions/18 for previous discussions around sync apis.

it might still be easier to add support for that in get-tsconfig (a little surprised it isn't supported yet) than bringing sync support to tsconfck. There is an old branch...

closing this as out of scope, get-tsconfig gives you sync access until eslint allows you to work async and anything that is related to interpreting the outcome of tsconfig needs...