Closed edemaine closed 2 months ago
On the other hand, I currently can't get VSCode to parse these files with these changes (because it's refusing to use updated Civet in
node_modules
), so can't get TS feedback, so we might want to fix that first...
I had a similar problem recently and had to quit and restart VSCode which seemed to fix it... 🤷
I figured out the issue: when running the VSCode on the Civet repo (at least when that repo is npm link
ed?), I get the live version of Civet from that repo in dist
. I hadn't run yarn build
in a while, so I wasn't getting the updates, despite the version number appearing correct.
I think these show some nice examples of
is like
.On the other hand, I currently can't get VSCode to parse these files with these changes (because it's refusing to use updated Civet in
node_modules
), so can't get TS feedback, so we might want to fix that first...