Skip to content

Releases: somewhatabstract/checksync

v6.0.0

15 Jun 00:29
07994cd
Compare
Choose a tag to compare

Major Changes

v5.0.5

04 Sep 00:17
9851b53
Compare
Choose a tag to compare

Patch Changes

v5.0.4

12 Jun 15:25
9b1fbb9
Compare
Choose a tag to compare

Patch Changes

v5.0.3

12 Jun 00:47
70aa5a1
Compare
Choose a tag to compare

Patch Changes

  • 003a91a: Fix rollup config to bundle deps

v5.0.2

12 Jun 00:31
c25f2d5
Compare
Choose a tag to compare

Patch Changes

v5.0.1

12 Jun 00:21
Compare
Choose a tag to compare

Note: There is no v5.0.0. v5 of Checksync uses a new automated publishing setup and that didn't work for the v5.0.0 release. The changes that were in v5.0.0 have been listed below with the v5.0.1 changes.

Major Changes

  • 6b561be: Migrate to TypeScript

    Although there are no functional changes here, we are bumping the major version since changing our static types are provided from Flow to TypeScript could break some folks development setups.

  • 14bbc5f: Working directory updates

    • The location of the configuration file is now used as the current working directory, if a configuration file is used. This means that globs are resolved relative to the configuration file, not the current working directory of the process launching checksync, which makes for a more deterministic behavior for
      folks trying to define and use their config files.
    • A --cwd argument has been added for specifying the working directory in cases where a configuration file is not used, or the configuration file discover needs to start in a place other than where checksync is invoked. If a configuration file is loaded, the location of that file takes precedence.
  • 95d1a29: Update gitignore support to support full range of syntax. We now use the ignore package to support the gitignore file syntax. New verbose logging has been added to help debug ignore file issues, too.

Patch Changes

  • 9534465: Improved console output to make things easier to read/scan
  • 52ddefd: Updating some things to get automated changeset release working

v3.0.1

27 Dec 01:12
Compare
Choose a tag to compare

This fixes the regex in the config file JSON schema so that it supports paths that include files like .gitignore. 🤦🏻‍♂️

Full Changelog: v3.0.0...v3.0.1

v3.0.0

27 Dec 00:34
Compare
Choose a tag to compare

🔗 CheckSync v3 is here! 🎉

This is a major update as we've overhauled the architecture, fixed bugs in "glob" handling, dropped Node 10 support, and more.

Huge thanks to @kevinbarabash and @jeremywiebe for their contributions and feedback during development.

What's New

  • Configuration file support
    When using CheckSync on complex projects, the command line arguments can get a bit unwieldy. To help manage this complexity, CheckSync v3 now supports a .checksyncrc configuration file. By default, CheckSync will look for a configuration file named .checksyncrc or .checksyncrc.json based on the current working directory and the root marker location. However, you can specify it via the --config CLI option if you want something different.

    In addition, a JSON schema is included to document the configuration format and it is used to validate your configurations.

  • Overhauled architecture with more auto-fixes and exported API
    The CheckSync parsing, fixing, and output architectures have all been reworked to separate concerns and allow for a greater variety of fixes besides just updating a checksum. This has also fixed a number of bugs around correctly handling duplicate tags, outputting all parsing results when there are errors, and more. This also means CheckSync is no longer CLI only; a simple API is now exported to allow you to invoke CheckSync programmatically within your own Node programs (or even tests).

    This overhaul should also improve maintenance of the code, including adding new features. However, there is a performance hit and we have noted v3 is a little slower than v2. We're hoping to focus on improving performance in upcoming patches.

  • Improved JSON output
    The JSON output has been standardized so that it can represent the various errors and autofixes that we may want to describe. This means that a caller (such as an eslint rule) will have all the information required to highlight errors and provide autofixes within the JSON output. Together with the exported API, this should make integrating CheckSync into linters and other environments much easier.

  • Support for globs when specifying ignore files
    Using the --ignore-files CLI option, you can now specify .gitignore-style files from subdirectories using glob syntax.

  • Correct glob handling
    CheckSync v2 was using the .gitignore-style of glob handling which was not really correct. CheckSync v3 treats globs that it receives the way it should.

Changelog

Features

Fixes

Maintenance

General

Dependency Updates by @dependabot

Read more

v2.3.0

08 Jun 21:37
Compare
Choose a tag to compare
  • Adds --json for outputting results as JSON
  • Adds --version for outputting current version of checksync

Thanks to @kevinbarabash for his work implementing JSON output.

v2.2.3

17 Jun 16:59
Compare
Choose a tag to compare

280d10c Update to [email protected] and update this to v2.2.3