-
Notifications
You must be signed in to change notification settings - Fork 450
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
Npm script type-check
is not working
#267
Comments
type-check
not workingtype-check
is not working
Confirmed |
This seems to be a regression in 3.6.2. It works fine with |
A temporary workaround (from poking around in #181), in package.json scripts:
|
I always thought my changes were causing the problem until I created a new project. Only to find out that brand new projects also have this problem |
Any progress? This is stopping us from using latest version. |
Fixes #267 Thanks @segevfiner for noticing this new feature! Currently there's still a small annoyance that `vue-tsc` would output an extra error message when there're type errors in `.vue` files vuejs/language-tools#2622 But it works well if there's no error. I've already submitted a PR to address it vuejs/language-tools#3176
Sorry that somehow I missed the notification a few days ago. It's because I moved the There are a few ways to fix it:
|
Fixes #267 It's because I moved the `compilerOptions` from `tsconfig.json` to `tsconfig.app.json` in the 2023-05-05 (v3.6.2) release, but forgot to change the `type-check` script. This isn't comprehensive because it doesn't check all the sub-projects, but at least it's the same scope as previous versions. Ideally I hope #274 can work reliably. But now I'm not sure. So let's first fix this bug.
Steps to reproduce:
npm init
create-vue@latest
, currently it is3.6.3
npx create-vue --ts --router --pinia --eslint-with-prettier source
and switch tosource
directorynpm run type-check
There are no errors reported by command.
The text was updated successfully, but these errors were encountered: