mirror of
https://github.com/loot/loot.github.io.git
synced 2026-07-27 14:13:30 -07:00
Use NPM to manage their versions: manually vendoring the libraries isn't feasible for Octokit, as its libraries aren't provided as single-file imports, and have nested dependencies of their own. Since NPM is needed to resolve that, use it for the other dependencies too. Hugo's built-in bundling and minification support is used, though it means that the dependencies are duplicated within the scripts imported on different pages. I think that could be avoided by introducing a middle layer of JS assets that bundle the dependencies but aren't bundled themselves.
19 lines
980 B
HTML
19 lines
980 B
HTML
---
|
|
layout: page
|
|
title: LOOT Settings File Converter
|
|
---
|
|
|
|
<p>Convert your <code>settings.yaml</code> (used by LOOT v0.11.0 and earlier) to a <code>settings.toml</code> (used by LOOT v0.12.0 and later). Your <code>settings.yaml</code> can be found in <code>%LOCALAPPDATA%\LOOT\</code>, which LOOT's "Open Debug Log Location" menu option opens, and the <code>settings.toml</code> goes in the same directory.</p>
|
|
|
|
<section>
|
|
<h3>YAML</h3>
|
|
<textarea id="input">Drag 'n' drop (or paste the contents of) your settings.yaml here.</textarea>
|
|
</section>
|
|
|
|
<section>
|
|
<h3>TOML <a id="download" download="settings.toml"></a></h3>
|
|
<textarea id="output" readonly></textarea>
|
|
</section>
|
|
|
|
<p>Note that the download link that appears above after converting YAML does not work in Internet Explorer or Edge. Users of those browsers will need to copy the content of the TOML text box into a <code>settings.toml</code> file they create themselves, or use a different browser</code>.</p>
|