Skip to content

v1.4.0
Compare
Choose a tag to compare
@github-actions github-actions released this 17 Jan 18:50
v1.4.0
2be7430

Important Changes

  • Starting with 1.4.0, the JS, CSS, and WASM files at the root of the files.stork-search.net CDN will no longer be updated. From this release going forward, you will need to change your <script> tags and <link rel="stylesheet"> tags to upgrade to a new version of Stork. See this Github announcement for more details.

New Features

  • Configuration files can now be in JSON format, in addition to TOML format
  • The web library now takes the number of occurrences in each file into account when ordering search results.
  • CLI: The --json flag for the search subcommand is now deprecated, as it did nothing in previous versions of Stork.
  • CLI: A new command line option for the search subcommand, --format <VALUE>, now determines how search results will be displayed in the terminal. The default value is json, which will display the search results in the JSON format understood by the browser module. A new value, pretty, will format the search results in a readable, understandable way. In the 2.0.0 Stork release, pretty will be the default value for this flag.
  • Two new CSS themes, edible and edible-dark, have been added. See https://stork-search.net/themes for examples and instructions on how to integrate them into your project.

Bug Fixes

  • Removes a stray console.log from the Javascript application
  • Fixes a Javascript runtime bug where registered indexes weren't always reporting as ready
  • Fixes a crash when the indexed contents contained words longer than 128 characters
  • The --timings flag previously did nothing. Now, when included with the build or search subcommands, timing information will be displayed at the end of the terminal output via stderr.
  • Document titles that were comprised of several words separated by hyphens would crash the search interface. This has been fixed.
Assets 13