| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| edible.css | 2022-01-17 | 5.0 kB | |
| flat.css | 2022-01-17 | 3.9 kB | |
| stork.js.map | 2022-01-17 | 66.8 kB | |
| basic.css | 2022-01-17 | 4.3 kB | |
| dark.css | 2022-01-17 | 4.5 kB | |
| edible-dark.css | 2022-01-17 | 5.2 kB | |
| stork-amazon-linux | 2022-01-17 | 6.7 MB | |
| stork.js | 2022-01-17 | 21.9 kB | |
| stork.wasm | 2022-01-17 | 316.4 kB | |
| stork-ubuntu-20-04 | 2022-01-17 | 10.4 MB | |
| stork-macos-10-15 | 2022-01-17 | 9.9 MB | |
| README.md | 2022-01-17 | 1.9 kB | |
| v1.4.0 source code.tar.gz | 2022-01-17 | 315.0 kB | |
| v1.4.0 source code.zip | 2022-01-17 | 369.4 kB | |
| Totals: 14 Items | 28.1 MB | 0 | |
Important Changes
- Starting with 1.4.0, the JS, CSS, and WASM files at the root of the
files.stork-search.netCDN 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
--jsonflag for thesearchsubcommand is now deprecated, as it did nothing in previous versions of Stork. - CLI: A new command line option for the
searchsubcommand,--format <VALUE>, now determines how search results will be displayed in the terminal. The default value isjson, 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,prettywill be the default value for this flag. - Two new CSS themes,
edibleandedible-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.logfrom 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
--timingsflag previously did nothing. Now, when included with thebuildorsearchsubcommands, 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.