Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Linter not showing errors on OS X #172

Open
sbking opened this issue May 23, 2017 · 6 comments
Open

Linter not showing errors on OS X #172

sbking opened this issue May 23, 2017 · 6 comments

Comments

@sbking
Copy link

sbking commented May 23, 2017

Debug output:

Platform: darwin
Atom Version: 1.17.0
Linter Version: 2.1.4
All Linter Providers: 
  - TSLint
Matching Linter Providers: 
  - TSLint
Disabled Linter Providers; 
Current File scopes: 
  - *
  - source.tsx

On my Arch Linux machine with identical .atom directory, it is working fine. On this mac, I just see a constant spinning circle, and when I hover over that I see:

Current:
tslint on foo.tsx

But no tslint errors are shown in any way. Oddly, if the "Fix errors on save" option is enabled, certain errors like whitespace issues are fixed on save but never shown in the editor.

If I disable the "Try using the local tslint package" option, the linter shows errors but only on save.

@Arcanemagus
Copy link
Member

What version of tslint do you have installed in your project?

@Xapphire13
Copy link
Contributor

The constant spinning circle means that the worker thread got hung up somewhere. I have a fix for this checked in, will be in v1.5.0 (about to release now). After that, the console should also tell you the error that TSLint itself is hitting

@Xapphire13
Copy link
Contributor

Please try now with v1.5.0 =]

@sbking
Copy link
Author

sbking commented May 27, 2017

@Xapphire13 @Arcanemagus With 1.5.0 the error was caught, apparently tslint was thinking the file I was editing was a directory and was causing an ENOTDIR error. I updated to tslint 5.3.2, which gets rid of that error when I use the local tslint.

However, the linting still only happens when I save. Typescript errors from the atom typescript package show immediately as I type them, but tslint errors aren't shown until a few seconds after I save. Is this normal? I'm pretty sure on my linux machine they show on change rather than save.

@Xapphire13
Copy link
Contributor

Hmm that's odd. On my machine linting errors appear real-time. I don't have access to a Mac to test on unfortunately either. Are both your Mac and Linux boxes using the same version of linter and linter-ui?

@bfricka
Copy link

bfricka commented Jul 10, 2019

I have this exact issue:
tslint -c tslint.json -t verbose src/**/*.{ts,tsx} shows some errors on Mac. But later, in CI environment the rest of the errors show up.

echo src/**/*.{ts,tsx} outputs all the right files so these should be getting to the CLI, but they aren't.

Edit: As mentioned here, The fix for me was to quote the glob string. Hopefully that works for you.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants