Bumps [js-beautify](https://github.com/beautifier/js-beautify) from
1.14.11 to 1.15.1.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/beautifier/js-beautify/blob/main/CHANGELOG.md">js-beautify's
changelog</a>.</em></p>
<blockquote>
<h2>v1.15.1</h2>
<ul>
<li>Turn new angular templating off by default in html (<a
href="https://redirect.github.com/beautifier/js-beautify/pull/2247">#2247</a>)</li>
<li>Perf regression in latest release (1.15.0) (<a
href="https://redirect.github.com/beautifier/js-beautify/issues/2246">#2246</a>)</li>
</ul>
<h2>v1.15.0</h2>
<ul>
<li>Fixed <a
href="https://redirect.github.com/beautifier/js-beautify/issues/2219">#2219</a>
- formatting of new Angular control flow syntax (<a
href="https://redirect.github.com/beautifier/js-beautify/pull/2221">#2221</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="8ebec7e81a"><code>8ebec7e</code></a>
Release: 1.15.1</li>
<li><a
href="f11af53db1"><code>f11af53</code></a>
Merge remote-tracking branch 'origin/staging/main' into
staging/release</li>
<li><a
href="9d4b333b69"><code>9d4b333</code></a>
Merge remote-tracking branch 'origin/release' into staging/release</li>
<li><a
href="f53ce3a5ff"><code>f53ce3a</code></a>
Bump version numbers for 1.15.1</li>
<li><a
href="5b41158f2e"><code>5b41158</code></a>
Update Changelog</li>
<li><a
href="5150015660"><code>5150015</code></a>
Merge pull request <a
href="https://redirect.github.com/beautifier/js-beautify/issues/2247">#2247</a>
from bitwiseman/feat/angular-off-default</li>
<li><a
href="5233c8f5f4"><code>5233c8f</code></a>
Add test for angular css conflict</li>
<li><a
href="96340d5d43"><code>96340d5</code></a>
Turn off new angular templating by default in html</li>
<li><a
href="b4775c33a1"><code>b4775c3</code></a>
Merge pull request <a
href="https://redirect.github.com/beautifier/js-beautify/issues/2235">#2235</a>
from beautifier/dependabot/github_actions/actions/ca...</li>
<li><a
href="87d3796bbc"><code>87d3796</code></a>
Merge pull request <a
href="https://redirect.github.com/beautifier/js-beautify/issues/2245">#2245</a>
from beautifier/dependabot/npm_and_yarn/webpack-5.90.2</li>
<li>Additional commits viewable in <a
href="https://github.com/beautifier/js-beautify/compare/v1.14.11...v1.15.1">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
</details>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Use hugo.toml instead of config.toml
Use the file hugo.toml in both the README.md and the exampleSite, since
Hugo will look for this file first.
The current instructions (using config.toml) in a new Hugo site
(that has a hugo.toml-file) means that the site doesn't work, or the
theme is not activated.
Note that this is a breaking change for sites running on older versions.
(But v0.110.0 was released almost a year ago.)
Relevant Hugo commit:
f38a2fbd2e
* Require `hugo v0.110.0`
> Make hugo.toml the new config.toml
see https://github.com/gohugoio/hugo/releases/tag/v0.110.0
---------
Co-authored-by: Jan Raasch <425211+janraasch@users.noreply.github.com>
It turns out my original proposal for #20 was correct, but not for the
reasons I thought. We need to set both `background-color` and `color` to
`initial` on `div.highlight pre` because that's where Chroma sets those
colors (including the default `color` if configured). Setting to
`initial` there makes it so that if the selected style *doesn't*
configure a default color, we'll use the `initial` color, which is going
to be the right choice because the reason style author left that unset
because they didn't consider dark color schemes messing with their
style. Then we `unset` the colors on `div.highlight code` because
otherwise the `code` colors from the theme will override the colors that
would otherwise be inherited from Chroma's `<pre>` element.
Stricly speaking I can't say that setting `background-color` to
`initial` is required, because I haven't found a Chroma style that
*doesn't* set a `background-color`, but I figure it's possible (at least
for a light theme) and it makes sense to fix it just in case, and causes
no harm otherwise.
