You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Spent a few hours debugging why linter wasn't working (not linting, not showing any UI whatsoever, no errors in the console).
Finally downgraded linter via apm install [email protected], and was then prompted by atom to install linter-ui-default, busy-signal and intentions. Was then able to upgrade 3.2.3 with everything working.
Did the dependency check code break in 3.2?
OS X Big Sur
Atom 1.53.0
Worst case, would be good to document on the primary readme that these packages are required.
The text was updated successfully, but these errors were encountered:
I can confirm exactly the same thing happened to me. New fresh Atom install on a new fresh Ubuntu 20.10 install on a PC. Didn't ask to automatically install dependencies. I stepped back down to [email protected] as suggested in @azielman 's post above. On first run asked to install those dependencies and things work just fine now.
Similar thing happening here (Ubuntu 20.4.2, atom 1.57.0).
When I installed linter I was not told to install linter-ui-default and no linting worked (and no errors or warnings of any kind appeared. it simply displayed no output).
When I installed manually linter-ui-default I got prompted to install intentions and busy-signal as dependencies.
Spent a few hours debugging why linter wasn't working (not linting, not showing any UI whatsoever, no errors in the console).
Finally downgraded linter via
apm install [email protected]
, and was then prompted by atom to installlinter-ui-default
,busy-signal
andintentions
. Was then able to upgrade 3.2.3 with everything working.Did the dependency check code break in 3.2?
OS X Big Sur
Atom 1.53.0
Worst case, would be good to document on the primary readme that these packages are required.
The text was updated successfully, but these errors were encountered: