-
Notifications
You must be signed in to change notification settings - Fork 4
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 run lint may not output error messages when running errors #29
Comments
binsee
added a commit
to binsee/chatie-git-scripts
that referenced
this issue
Apr 20, 2022
binsee
added a commit
to binsee/chatie-git-scripts
that referenced
this issue
Apr 20, 2022
After pr #30 ✘ binsee@shanmudeMBP15 ~/CodeWork/puppet-xp fix-git-scripts ± git push
[Step-1] Checking last commit...
[Step-2] Checking lint...
Error:
------------------------------------------
> [email protected] lint
> npm run lint:es && npm run lint:ts && npm run lint:md
> [email protected] lint:es
> eslint "src/**/*.ts" "tests/**/*.spec.ts" --ignore-pattern tests/fixtures/
> [email protected] lint:ts
> tsc --isolatedModules --noEmit
examples/ding-dong-bot.ts(113,5): error TS2339: Property 'talkerId' does not exist on type 'MessagePayload'.
src/puppet-xp.ts(307,7): error TS2322: Type '{ id: string; roomId: string; talkerId: string; text: string; timestamp: number; toId: string; type: PUPPET.type.Message.Unknown | PUPPET.type.Message.Audio | PUPPET.type.Message.Contact | ... 4 more ... | PUPPET.type.Message.Video; }' is not assignable to type 'MessagePayload'.
Object literal may only specify known properties, and 'talkerId' does not exist in type 'MessagePayload'.
------------------------------------------
Failed to exec pre-push hook script
error: 无法推送一些引用到 'github.com:binsee/puppet-xp.git' |
I ran into this problem today as well, thank you very much for the improvement! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running npm lint fails with no error message
So, error message for
tsc --isolatedModules --noEmit
not output to stderr, but output to stdout.We need to be compatible with the message output to stdout when stderr has no message.
The text was updated successfully, but these errors were encountered: