Bot releases are visible (Hide)
Published by jfmengels over 4 years ago
https://github.com/jfmengels/node-elm-review/compare/v2.2.0-beta0...v2.2.0-beta2
Published by jfmengels over 4 years ago
Adds 2 new subcommands:
new-package
: Creates a new package aimed at publishing elm-review
rulesnew-rule
: Adds a new rule to your review configuration/projectIndividual commits
https://github.com/jfmengels/node-elm-review/compare/v2.1.4...v2.2.0-beta0
Published by jfmengels over 4 years ago
In some cases, the output of the report (in non-json output) got hidden, and you couldn't see the text in the terminal.
I haven't investigated enough, but basically, it's because of trying to wrap a colored output with terminal link which ended up creating this problem.
This problem was introduced in v2.1.2
Individual commits:
https://github.com/jfmengels/node-elm-review/compare/v2.1.3...v2.1.4
Published by jfmengels over 4 years ago
The compilation now happens in a temporary folder, getting rid of the review application's compilation artifacts inside elm-stuff
(one that is nested in your project's elm-stuff
)
https://github.com/jfmengels/node-elm-review/compare/v2.1.2...v2.1.3
Published by jfmengels over 4 years ago
Highlights
--ignore-problematic-dependencies
flag, to work around https://github.com/elm/project-metadata-utils/issues/12
--report=json
List of commits:
https://github.com/jfmengels/node-elm-review/compare/v2.1.1...v2.1.2
Add files that were not published and prevented the CLI from working.
https://github.com/jfmengels/node-elm-review/compare/v2.1.0...v2.1.1
New requirement, this version of node-elm-review
requires you to use at least version 2.1.0
of the jfmengels/elm-review
package. This is necessary to add new features useful for JSON reporting. You can run the following commands to update it.
cd your-project/
cd review/
npx elm-json install jfmengels/elm-review@2
--report=json
to get a report in the JSON format. This will pave the way to supporting running elm-review
in editors (🎉) and other environments than just the terminal.node-elm-review
https://github.com/jfmengels/node-elm-review/blob/master/documentation/tooling-integration.md.elm-review
, the files that are not parsed into ASTs (and cached) yet get parsed. This is now done in parallel in separate worker_threads. This will not be available if you use Node.js v10, but it will if you use v12 or higher (due to the availability of worker_threads
).worker_thread
, which we can dispose of to avoid memory leaks. Changing your configuration while in watch should now not increase the memory usage until it all explodes. Also, re-running after the configuration has changed should be a bit faster now.elm-format
is now applied to the fixed files without it first being written to the file system. Much thanks to @sparksp for tackling this! (I failed at making this work months ago and he made it work easily. That's embarassing.)ELM_HOME
. These are now downloaded and cached separately. This should let you run elm-review
while offline.elm-format
after saving to the file system 8a04fb3npx --no-install
aa394e7-local
suffix 3348804https://github.com/jfmengels/node-elm-review/compare/v2.0.2......v2.1.0
Published by jfmengels over 4 years ago
npx --no-install
aa394e7-local
suffix 3348804https://github.com/jfmengels/node-elm-review/compare/v2.0.2...v2.1.0-beta.1
elm-explorations/test
not being properly removed on init fb531b4https://github.com/jfmengels/node-elm-review/compare/v2.0.1...v2.0.2
Highlight:
Made it possible to run elm-test
with elm-review init
. A bug in elm-test
prevents that.
Warn about readme changing only in debug mode c30c7aa
Make tests pass on other machines 64c5a89
Delete 'elm-explorations/test' from indirect deps on init 597b2dc
Install latest compatible elm/core and elm/json on init 32bd912
https://github.com/jfmengels/node-elm-review/compare/v2.0.0...v2.0.1
Changes:
https://github.com/jfmengels/node-elm-review/compare/v2.0.0-beta.1...v2.0.0
Published by jfmengels over 4 years ago
Blog post announcing all the new things will be available in the non-beta v2.0.0 release.
elm.json
could be found 1d95653elm.json
f2d5c79elm-json
solve 41df5e9https://github.com/jfmengels/node-elm-review/compare/v1.0.2...v2.0.0-beta.1
A few improvements:
elm-review
package that is compatible with the CLI. This is to prepare for a new major version. Previous versions of node-elm-review
will likely break once that version is released, so I highly suggest you update your version to at least this one before then 5c185e1stil4m/elm-syntax
and elm/project-metadata-utils
) are now installed as direct dependencies, which should make it a bit easier to start writing your own rules 8e5cb93https://github.com/jfmengels/node-elm-review/compare/v1.0.1...v1.0.2