All notable changes to this project will be documented in this file. This project adheres to Semantic Versioning.
- 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