-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Add vite.config.[ts|js] will cause vuedx-typecheck fail #133
Comments
The original issue closed on vite and suggested I should test on vite 2.0 beta and reopen if this is still an issue. I just tested on vite 2.0.0.-beta.1 and I still got the same issue. However, this look like more of an issue in vuedx-typecheck, so I will add any further comment here instead. |
Things are moving fast.. I tried on vite 2.0.0-beta.2 which just release less than an hour ago and it still failed. However, it seems that if I remove "dist" directory before I run vuedx-typecheck, everything work fine. I think the issue is located in diagnostics.ts, add the dist directory in ignore on line 113 should fix the issue:
But I cannot seems to build vue-developer-experience successfully on my fork (got some rollup fail message when try to build it), so I cannot verify it for now. |
Describe the bug
If you add vite.config.ts to the project, the vuedx-typecheck will fail during "yarn build"
Note that I created the issue on vite, but after digging a little bit more it appear to be vuedx-typecheck issue.
To Reproduce
Steps to reproduce the behavior:
At this point everything work fine as expected.
Now create an empty vite.config.js (or .ts) run yarn build again and it will fail (log is too big to attach, but it output something like this)
If I remove vuedx-typecheck in package.json build step, the build run fine, and obviously if I run "yarn run vuedx-typescript .", it will fail as well.
I also try to put something in vite.config.js like the example provided in README
It still fail.
Expected behavior
Build should not fail.
Info (please complete the following information):
The text was updated successfully, but these errors were encountered: