Bot releases are visible (Hide)
Published by jfmengels over 3 years ago
Individual commits
https://github.com/jfmengels/node-elm-review/compare/v2.4.0...v2.4.1-beta.1
Published by jfmengels over 3 years ago
https://github.com/jfmengels/node-elm-review/compare/v2.4.1-beta.1...v2.4.1-beta.2
Published by jfmengels over 3 years ago
Individual commits
https://github.com/jfmengels/node-elm-review/compare/v2.4.0...v2.4.1-beta.1
Published by jfmengels almost 4 years ago
I added an entry in the --help
for --report=json
, which makes elm-review
print a big JSON instead of the human-readable report you're used to, allowing for other tools to make use of it. This feature already existed but wasn't documentated.
I also added a new report mode --report=ndjson
. Instead of printing one big JSON with all the errors, the CLI will instead print each error on a separate line. This can be useful if you want to send elm-review
errors to a logging system for instance.
Both of these are described in detail in the dedicated tooling integration document.
elm-json
, which is used to compute the dependencies when building your configuration, is now not a dependency of this project anymore. Instead, we depend on @lydell's recently released elm-tooling
, which downloads elm-json
automatically or re-uses the one you already have on your system if available. This reduces the size of elm-review
's node_modules
from 20MB to 5.9MB!
I think elm-review
will using elm-tooling
more and more. Thanks a lot for both the tool and the PR @lydell!
elm-review
would exit without having printed everything when using --report=json
(thanks to @arkham)elm-review
from somewhere else than the root of the project.new-package
-created projects runnable on Windows (thanks to @fredericbonnet)https://github.com/jfmengels/node-elm-review/compare/v2.4.0-beta.1...v2.4.0-beta.2
Published by jfmengels about 4 years ago
https://github.com/jfmengels/node-elm-review/compare/v2.3.3...v2.4.0-beta.1
Published by jfmengels about 4 years ago
https://github.com/jfmengels/node-elm-review/compare/v2.3.2...v2.3.3
Published by jfmengels about 4 years ago
https://github.com/jfmengels/node-elm-review/compare/v2.3.1...v2.3.2
https://github.com/jfmengels/node-elm-review/compare/v2.3.0...v2.3.1
https://github.com/jfmengels/node-elm-review/compare/v2.3.0-beta.3...v2.3.0
Published by jfmengels about 4 years ago
https://github.com/jfmengels/node-elm-review/compare/v2.3.0-beta.2...v2.3.0-beta.3
--template
now supports running with and initializing with configurations that link to parent directories (like "source-directories": ["src", "../src"]
)
The default configuration created by elm-review new-package
now contains more rules.
After first parsing a file, we store the parsed AST in the file system under elm-stuff
, so that we can avoid having to do the expensive parsing at every run. Previously, we were using elm-syntax
's encoder/decoder for that, but the total size of the cache was pretty big (roughly 6 to 8 times the total size of the Elm files of the project), which was a lot of data to load from the file system, which is a slow process.
Thanks to @MartinSStewart's hard work on elm-serialize
and on integrating it with elm-review
, we now write a way more compressed version of the AST, which is about a third of what it was before. On a 160k LoC project, that went from 41MB of data to about 14MB. This cuts roughly 15% of the time both on the first initial run (writing the files is faster) and on the successive runs (loading the files is faster).
https://github.com/jfmengels/node-elm-review/compare/v2.3.0-beta.1...v2.3.0-beta.2
https://github.com/jfmengels/node-elm-review/compare/v2.2.6...v2.3.0-beta.1
Published by jfmengels over 4 years ago
https://github.com/jfmengels/node-elm-review/compare/v2.2.5...v2.2.6
Published by jfmengels over 4 years ago
A crash would occur after the initial compilation of the configuration, which is a regression introduced in v2.2.4.
Additional improvements:
node_modules
too 565fc4ahttps://github.com/jfmengels/node-elm-review/compare/v2.2.4...v2.2.5
Published by jfmengels over 4 years ago
https://github.com/jfmengels/node-elm-review/compare/v2.2.3...v2.2.4
https://github.com/jfmengels/node-elm-review/compare/v2.2.2...v2.2.3
Published by jfmengels over 4 years ago
https://github.com/jfmengels/node-elm-review/compare/v2.2.1...v2.2.2
Published by jfmengels over 4 years ago
This fixes #12, which reported that Elm files in node_modules
were not getting included even when they were present in the elm.json
's source-directories
.
Full commit list:
https://github.com/jfmengels/node-elm-review/compare/v2.2.0...v2.2.1
Published by jfmengels over 4 years ago
First of all, there are 2 new subcommands:
new-package
: Creates a new package aimed at publishing elm-review
rulesnew-rule
: Adds a new rule to your review configuration/projectThese aim to help you create good rules and consistent review packages. Try them out, and let us know what you think!
--no-details
hides the details from an error message.elm-json
has been upgraded to 0.2.7
, which contains a lot of performance improvements that elm-review
will benefit from.https://github.com/jfmengels/node-elm-review/compare/v2.1.4...v2.2.0