All notable changes to this project will be documented in this file. This project adheres to Semantic Versioning.
TypeError
under certain circumstances on path-less files (7780e7c
)
- Support for TypeScript (
488c1c0
, #225)
- Setting to disable style-specific settings in
package.json
(it now always honors settings inpackage.json
) (e87d36b
) - Support for standard-flow (
0df4d9b
)
- Support for Atom’s experimental Tree-sitter parsing system (
46c8038
)
filename
is now passed tolintText()
which is required by some linters and ESLint plugins (see also v4.1.0 and v4.2.0) (64e11fd
, #213, #212)
- No longer lints hidden files and folders by default (see #214)
- Updated the bundled
standard
to v11 (df21570
) - Updated the bundled
babel-eslint
to v8 (3338959
) - Updated the bundled
esprima
to v4 (1c99b14
)
- Support for uber-standard (
eea8bfe
)
The change in v4.1.0 turned out to be backwards-incompatible. Therefore, v4.2.0 reverts this change. It will be added back in the next major release.
filename
is now passed tolintText()
which is required by some linters and ESLint plugins (64e11fd
, #213, #212)
envs
not being recognized inpackage.json
(7f4cda6
)envs
not being recognized when specified as an object (0f1a5ab
, #209)
- Errors when the editor’s contents were modified while the linter was running (
2d6af60
,05f787f
, #200) - Not ignoring whole directories when specified in
standard.ignore
inpackage.json
(switched to ignore,f7481f5
) (#206) - Other ignore-related fixes (see Why another ignore?) (switched to ignore,
f7481f5
)
Errors when the editor’s contents were modified while the linter was running (Did not actually fix the issue, see #200 (comment)2d6af60
, #200)
- Link to ESLint rule documentation (
77d728d
, #181) - Setting to disable linter if the project already uses ESLint (
7444f86
, #197, #194) - Show an error notification when installation of linter fails (updated atom-package-deps to v4,
6baf9d1
)
- Convert all warnings to errors (making linter-js-standard more consistent with standard itself) (
9fc542c
) - Considerably improved range highlighting (
24e76ae
,e5d31dc
, #74) - Slightly improved settings’ titles and descriptions (
cd3b121
,ac98c09
) - Prompt before installing the linter dependency (updated atom-package-deps to v4,
6baf9d1
) - Bumped minimum required Atom version to v1.14.0 (
8522c0c
) - Bumped required Linter version to v2 (
be7b9e9
,c7b2213
) - Updated the bundled
standard
to v10 (53ede59
) - Updated the bundled
semistandard
to v11 (f610c1d
) - Updated the bundled
happiness
to v10 (ca413a2
)
- Support for Esprima-FB (
cc42217
)
- Issues when installing linter on newer Atom versions (updated atom-package-deps to v4,
6baf9d1
) (#187) - Re-use last messages if linter throws an error (avoids “Linter Result must be an Array” error) (
32e8b75
)
- Linting with standard-flow when it is not locally installed (
edb3127
, #166)
- Uncaught
TypeError
when switching back to a file which has been deleted in the background (3c9ad13
, #168) - “Something went wrong” warning upon opening a file for the first time after opening a new window (
e51f30b
, #179)
- Annoying repeating warnings.
- find-root package
- Dependencies update:
- ⬆️ standard@^8
- Dependencies update:
- ⬆️ esprima@^3
- ⬆️ babel-eslint@^7
- ⬆️ happiness@^7
- ⬆️ semistandard@^9
- find-root package
- Option
checkDevDependencies
default totrue
- Dependencies:
- atom-package-deps@^2.0.5
NOTE: From this version and on
linter-js-standard
doesn't needlinter
installed beforehand.
- Dependencies update:
- Semistandard stop working after you use standard style
- Linter doesn't lint when
Markdown linting
option is disabled
- Support fenced code lint in markdown files
- Annoying warning message in issue #37
- Subscription event to cache file package.json settings to
.onDidChangeActivePaneItem
. This solved issue #37 - Use the linter's node.js API instead of a
child_process.execFile()
call, making the linter supaaa fast! Partially suggested in issue #38. - Use a static version for the linters instead of
^x.x.x
- New setting
showEslintRules
: Enable/disable show eslint rule name- Feature requested in issue #39
- Dependencies update
- ⬆️ standard@^5.0.0
- ⬆️ semistandard@^7.0.2
- Switched from using file path to
stdin
- Dependencies update
- ⬆️ atotm-linter@^3.0.0
- Fix permanently issue #30
- Support global vars in package.json
- Warning message
- Random errors thrown
no-style
wasn't working
- Still showing in
Deprecation Cop
that is needed to migrate to new API.- remove key
linter-package
from package.json
- remove key
- Transpile code base from coffescript to javascript
- AtomLinter new API migration
- happiness linter
- add
cache: false
to pkgConfig options
- Dependencies update
- New dependencies
- esprima
- esprima-fb
- More 2 custom parsers supported (esprima and esprima-fb)
- Reorganize code
- When option
checkDevDependencies
was ticked and it didn't find any style on package.json it would throw a random error
- Documentation
- Custom parser
babel-eslint
- Check project style in package.json
devDependencies
- Support to custom parser
babel-eslint
- Honor style settings
- Add keywords to package.json
- New dependencies
- minimatch
- pkg-config
- find-root
- babel-eslint
- Documentation
- Dependencies major update
path
is not defined- Related to a atom issue that was fixed in v0.199.0 release.
Fixed an issue where fs and path would be accidentally available as global variables
text.html.basic
from grammar scope
- Deprecate call to AtomLinter API
- replace key
activationEvents
toactivationCommands
in package.json
- replace key
- Documentation
- semistandard linter
- Change stream from
stderr
tostdout
soruce.js.jsx
files to grammarScope
- Update dependencies
- cwd
- Documentation
- Documentation
- standard linter