Closed JeromeDeLeon closed 1 year ago
@JeromeDeLeon the changes in #412 should fix the issue. I have released a temporary version. Could you try it and let me know if it works for you?
pnpm add vue-types@0.0.0-20230720044845
@JeromeDeLeon the correct PR is #421, sorry
Thanks @dwightjack. I just installed that build and it is now working.
@JeromeDeLeon I found a typo in the shim definition and fixed it in vue-types@0.0.0-20230721024211
, but the main entry point seems to work fine. I pushed a demo installation here: https://github.com/dwightjack/demo-vue-types, and I see it working correctly on VSCode (look at the src/components/Test.vue
component) and when running both the dev
and build
scripts.
If you're still experiencing the issue after installing vue-types@0.0.0-20230721024211
, could you share a reproduction?
@dwightjack Thanks, it is working for me. We pretty much have the same setup as you have on your demo.
Released as vue-types@5.1.1
.
Describe the bug I scaffolded the project using
pnpm create vue@latest
with the following optionsI then added
vue-types
right after and started using it and got an errorI tried looking for similar issues around
and I tried running
tsc --traceResolution
and gotbut I managed to get it working by doing this where I patched the
*.d.ts
to have similar location and file name of the.(c)js
filesand then re-run the
tsc --traceResolution
againI haven't tested the
require
or theshim
version but hopefully they work the same wayTo Reproduce Steps to reproduce the behavior:
vue-types
Expected behavior I'm expecting to not have this error
Library version