mirror of
https://github.com/alecthomas/chroma.git
synced 2025-01-28 03:29:41 +02:00
831 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Fredrare
|
a56e228d32
|
Update TypeScript lexer to allow nested generics (#1002)
https://github.com/alecthomas/chroma/issues/425 shows that generics are not correctly identified in general, but they are rather being treated as JSX elements. I proposed a simple solution in the comments by adding a space between `<` and the word next to it, but I believe most people will either not find the solution or some of them will find it rather unappealing. For this reason, I made the JSX rules recursive and added a `","` `Punctuation` token inside so that there can be a number of generics used, as well as allowing nested generics. While I am not really fond of this hack, given that generics are already treated as JSX elements, I think this is a fair and easy enough solution for most cases. #### Before <img width="359" alt="Screenshot 2024-09-20 at 9 28 05 PM" src="https://github.com/user-attachments/assets/b03c2c8a-3278-438b-8803-00eb62cc4a17"> #### With spacing solution <img width="392" alt="Screenshot 2024-09-20 at 9 30 13 PM" src="https://github.com/user-attachments/assets/89289476-c92a-41df-b893-5ab289fa96aa"> #### With recursive JSX and `","` `Punctuation` token <img width="362" alt="Screenshot 2024-09-20 at 9 55 11 PM" src="https://github.com/user-attachments/assets/d77d892e-667d-4fb4-93cf-8227d5bd4b17"> |
||
Aru Sahni
|
10c0c524c4
|
Update the Materialize lexer (#1001)
Syncing over the latest keywords for the Materialize lexer. Thank you for the review! |
||
renovate[bot]
|
7a4d1d9cbf
|
chore(deps): update module github.com/alecthomas/kong to v1 (#999)
This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/alecthomas/kong](https://redirect.github.com/alecthomas/kong) | `v0.9.0` -> `v1.2.1` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>alecthomas/kong (github.com/alecthomas/kong)</summary> ### [`v1.2.1`](https://redirect.github.com/alecthomas/kong/compare/v1.2.0...v1.2.1) [Compare Source](https://redirect.github.com/alecthomas/kong/compare/v1.2.0...v1.2.1) ### [`v1.2.0`](https://redirect.github.com/alecthomas/kong/compare/v1.1.0...v1.2.0) [Compare Source](https://redirect.github.com/alecthomas/kong/compare/v1.1.0...v1.2.0) ### [`v1.1.0`](https://redirect.github.com/alecthomas/kong/compare/v1.0.0...v1.1.0) [Compare Source](https://redirect.github.com/alecthomas/kong/compare/v1.0.0...v1.1.0) ### [`v1.0.0`](https://redirect.github.com/alecthomas/kong/compare/v0.9.0...v1.0.0) [Compare Source](https://redirect.github.com/alecthomas/kong/compare/v0.9.0...v1.0.0) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/alecthomas/chroma). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC43NC4xIiwidXBkYXRlZEluVmVyIjoiMzguNzQuMSIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6W119--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> |
||
Konrad Reiche
|
ebd6894926
|
Update GitHub light color palette (#998)
I noticed that the current syntax highlighting generator uses an older color palette that doesn’t reflect GitHub’s latest light theme, which now features lighter, pastel tones for improved readability and accessibility. I’ve updated the color scheme to match the newer colors. I was wondering if it makes sense to adopt these changes or, if maintaining the current color scheme is essential, whether it would be better to publish this as a separate variant under a different name. ## Example ### Before  ### After  |
||
Jannis
|
a6994de218
|
add beef syntax and tests (#995)
This adds #994 Beeflang. The syntax itself is just a modifed version of c# with a few keywords added or removed. Also Ive added a test and run the test until it worked. I am unsure if the mime_type is relevant to keep in there since I dont know where that actually used. Another thing im unsure of is how the selection of what language/syntax to use for a file actually works aka: Does this actually choose Beef syntax highlighting over Brainfuck if its used on a beef (.bf) file ? for that I would probably need help. Co-authored-by: Booklordofthedings <Booklordofthedings@tutanota.com> |
||
|
renovate[bot]
|
9e60ae3cfc
|
chore(deps): update all non-major dependencies (#991)
[](https://renovatebot.com) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [esbuild](https://togithub.com/evanw/esbuild) | patch | `0.23.0` -> `0.23.1` | | [svu](https://togithub.com/caarlos0/svu) | minor | `2.1.0` -> `2.2.0` | --- ### Release Notes <details> <summary>evanw/esbuild (esbuild)</summary> ### [`v0.23.1`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0231) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.23.0...v0.23.1) - Allow using the `node:` import prefix with `es*` targets ([#​3821](https://togithub.com/evanw/esbuild/issues/3821)) The [`node:` prefix on imports](https://nodejs.org/api/esm.html#node-imports) is an alternate way to import built-in node modules. For example, `import fs from "fs"` can also be written `import fs from "node:fs"`. This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with `--target=node14` so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as `--target=node18,es2022` removes the `node:` prefix because none of the `es*` targets are known to support this feature. This release adds the support for the `node:` flag to esbuild's internal compatibility table for `es*` to allow you to use compound targets like this: ```js // Original code import fs from 'node:fs' fs.open // Old output (with --bundle --format=esm --platform=node --target=node18,es2022) import fs from "fs"; fs.open; // New output (with --bundle --format=esm --platform=node --target=node18,es2022) import fs from "node:fs"; fs.open; ``` - Fix a panic when using the CLI with invalid build flags if `--analyze` is present ([#​3834](https://togithub.com/evanw/esbuild/issues/3834)) Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the `--analyze` flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how `--analyze` is implemented) to a null build object. The panic has been fixed in this release. - Fix incorrect location of certain error messages ([#​3845](https://togithub.com/evanw/esbuild/issues/3845)) This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild. - Print comments before case clauses in switch statements ([#​3838](https://togithub.com/evanw/esbuild/issues/3838)) With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification). - Fix a memory leak with `pluginData` ([#​3825](https://togithub.com/evanw/esbuild/issues/3825)) With this release, the build context's internal `pluginData` cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return `pluginData` objects from `onResolve` and/or `onLoad` callbacks. </details> <details> <summary>caarlos0/svu (svu)</summary> ### [`v2.2.0`](https://togithub.com/caarlos0/svu/releases/tag/v2.2.0) #### Changelog ##### New Features - [`8e1fe56`]( |
||
Alec Thomas
|
cc157bfce4 | chore: upgrade go+golangci-lint | ||
Gusted
|
4d11870090
|
Don't output extra whitespace in YAML multiline (#993)
This resolves a particular issue with parsing YAML multiline, for example: ```yaml a: | multiline literal line 2 ``` The regex used would capture the amount of indentation in the third capture group and then use that as a kind of "status" to know which lines are part of the indented multiline. However, because its a captured group it has to be assigned a token which was `TextWhitespace`. This meant that the indentation was outputted after the multiline, technically it should be seen as an non-captured group, but then its no longer to refer to it in the regex. Therefore I've gone with the solution to add a new token, Ignore, which will not be emitted as a token in the iterator, which can safely be used to make use of capture groups but not have them show up in the output. ## Before  ## After  |
||
Koki Fukuda
|
895a0488b5
|
Port Minecraft lexers from Pygments (#992)
Ported lexers for mcfuntion, snbt from Pygments using `pygments2chroma_xml.py` script. While doing so, I encountered lack of `LiteralNumberByte` in TokenType, so I've added the type and regenerated tokentype_enumer.go. |
||
Mikko Ahlroth
|
763c2ea5e2
|
Add Gleam to README (#990) | ||
|
renovate[bot]
|
c6e90314df
|
chore(deps): update all non-major dependencies (#985)
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | Type | Update | |---|---|---|---|---|---|---|---| | [github.com/dlclark/regexp2](https://togithub.com/dlclark/regexp2) | `v1.11.2` -> `v1.11.4` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | require | patch | | [svu](https://togithub.com/caarlos0/svu) | `2.0.1` -> `2.1.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | minor | --- ### Release Notes <details> <summary>dlclark/regexp2 (github.com/dlclark/regexp2)</summary> ### [`v1.11.4`](https://togithub.com/dlclark/regexp2/compare/v1.11.3...v1.11.4) [Compare Source](https://togithub.com/dlclark/regexp2/compare/v1.11.3...v1.11.4) ### [`v1.11.3`](https://togithub.com/dlclark/regexp2/compare/v1.11.2...v1.11.3) [Compare Source](https://togithub.com/dlclark/regexp2/compare/v1.11.2...v1.11.3) </details> <details> <summary>caarlos0/svu (svu)</summary> ### [`v2.1.0`](https://togithub.com/caarlos0/svu/releases/tag/v2.1.0) #### Changelog ##### New Features - [`680777b`]( |
||
|
Aru Sahni
|
9221c6d919
|
Update the Materialize lexer (#987) | ||
Mikhail Sorochan
|
3044bf5f32
|
Go lexer: single line comment without consuming endline, disable EnsureNL (#984)
This PR changes `CommentSingle` to not consume the newline at the end as
a part of comment.
That solves the problems of single line comment being not parsed at the
end of the line or at the end of the file. Which was reported earlier as
the reason to not highlight single line comment properly.
Disabling `EnsureNL: true` does not add unnecessary newline element for
`Text`, `CommentSymbol` symbols. Using chroma in console with syntax
highlighting was unusable becasue of this, since typing e.g. `b := `
adds newline each time space is at the end when host app asks for
highlighted text from `quick`.
Tokens behavior:
<table>
<tr>
<td> Before </td> <td> After </td>
</tr>
<tr>
<td>
``` go
t.Run("Single space", func(t *testing.T) {
tokens, _ := chroma.Tokenise(Go, nil, " ")
expected := []chroma.Token{
{chroma.Text, " \n"},
}
assert.Equal(t, expected, tokens)
})
t.Run("Assignment unfinished", func(t *testing.T) {
tokens, _ := chroma.Tokenise(Go, nil, "i = ")
expected := []chroma.Token{
{ chroma.NameOther, "i" },
{ chroma.Text, " " },
{ chroma.Punctuation, "=" },
{ chroma.Text, " \n" },
}
assert.Equal(t, expected, tokens)
})
t.Run("Single comment", func(t *testing.T) {
tokens, _ := chroma.Tokenise(Go, nil, "// W")
expected := []chroma.Token{
{ chroma.CommentSingle, "// W\n" },
}
assert.Equal(t, expected, tokens)
})
```
</td>
<td>
``` go
t.Run("Single space", func(t *testing.T) {
tokens, _ := chroma.Tokenise(Go, nil, " ")
expected := []chroma.Token{
{chroma.Text, " "},
}
assert.Equal(t, expected, tokens)
})
t.Run("Assignment unfinished", func(t *testing.T) {
tokens, _ := chroma.Tokenise(Go, nil, "i = ")
expected := []chroma.Token{
{ chroma.NameOther, "i" },
{ chroma.Text, " " },
{ chroma.Punctuation, "=" },
{ chroma.Text, " " },
}
assert.Equal(t, expected, tokens)
})
t.Run("Single comment", func(t *testing.T) {
tokens, _ := chroma.Tokenise(Go, nil, "// W")
expected := []chroma.Token{
{ chroma.CommentSingle, "// W" },
}
assert.Equal(t, expected, tokens)
})
```
</td>
</tr>
</table>
|
||
Vlad Dimov
|
40e5e9989e
|
Add JSONata Lexer (#983)
Add lexer for [JSONata](https://docs.jsonata.org/overview.html) including test data. |
||
|
renovate[bot]
|
8c889434ec
|
chore(deps): update all non-major dependencies (#981)
[](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---|---|---| | [esbuild](https://togithub.com/evanw/esbuild) | | minor | `0.21.5` -> `0.23.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [github.com/dlclark/regexp2](https://togithub.com/dlclark/regexp2) | require | patch | `v1.11.0` -> `v1.11.2` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [go](https://togithub.com/golang/go) | | patch | `1.22.4` -> `1.22.5` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [watchexec](https://togithub.com/watchexec/watchexec) | | patch | `2.1.1` -> `2.1.2` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>evanw/esbuild (esbuild)</summary> ### [`v0.23.0`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0230) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.22.0...v0.23.0) ***This release deliberately contains backwards-incompatible changes.*** To avoid automatically picking up releases like this, you should either be pinning the exact version of `esbuild` in your `package.json` file (recommended) or be using a version range syntax that only accepts patch upgrades such as `^0.22.0` or `~0.22.0`. See npm's documentation about [semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more information. - Revert the recent change to avoid bundling dependencies for node ([#​3819](https://togithub.com/evanw/esbuild/issues/3819)) This release reverts the recent change in version 0.22.0 that made `--packages=external` the default behavior with `--platform=node`. The default is now back to `--packages=bundle`. I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future. In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development. - Fix preserving collapsed JSX whitespace ([#​3818](https://togithub.com/evanw/esbuild/issues/3818)) When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with `--jsx=preserve`. Here is an example: ```jsx // Original code <Foo> <Bar /> </Foo> // Old output (with --jsx=preserve) <Foo><Bar /></Foo>; // New output (with --jsx=preserve) <Foo> <Bar /> </Foo>; ``` ### [`v0.22.0`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0220) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.21.5...v0.22.0) **This release deliberately contains backwards-incompatible changes.** To avoid automatically picking up releases like this, you should either be pinning the exact version of `esbuild` in your `package.json` file (recommended) or be using a version range syntax that only accepts patch upgrades such as `^0.21.0` or `~0.21.0`. See npm's documentation about [semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more information. - Omit packages from bundles by default when targeting node ([#​1874](https://togithub.com/evanw/esbuild/issues/1874), [#​2830](https://togithub.com/evanw/esbuild/issues/2830), [#​2846](https://togithub.com/evanw/esbuild/issues/2846), [#​2915](https://togithub.com/evanw/esbuild/issues/2915), [#​3145](https://togithub.com/evanw/esbuild/issues/3145), [#​3294](https://togithub.com/evanw/esbuild/issues/3294), [#​3323](https://togithub.com/evanw/esbuild/issues/3323), [#​3582](https://togithub.com/evanw/esbuild/issues/3582), [#​3809](https://togithub.com/evanw/esbuild/issues/3809), [#​3815](https://togithub.com/evanw/esbuild/issues/3815)) This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for `--platform=node`) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use `--packages=external` to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this. With this release, esbuild will now omit packages from the bundle by default when the platform is `node` (i.e. the previous behavior of `--packages=external` is now the default in this case). *Note that your dependencies must now be present on the file system when your bundle is run.* If you don't want this behavior, you can do `--packages=bundle` to allow packages to be included in the bundle (i.e. the previous default behavior). Note that `--packages=bundle` doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using `--external:` even when `--packages=bundle` is present. The `--packages=` setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of `/` or `.` or `..` are considered to be package imports. The only two exceptions to this rule are [subpath imports](https://nodejs.org/api/packages.html#subpath-imports) (which start with a `#` character) and TypeScript path remappings via `paths` and/or `baseUrl` in `tsconfig.json` (which are applied first). - Drop support for older platforms ([#​3802](https://togithub.com/evanw/esbuild/issues/3802)) This release drops support for the following operating systems: - Windows 7 - Windows 8 - Windows Server 2008 - Windows Server 2012 This is because the Go programming language dropped support for these operating system versions in [Go 1.21](https://go.dev/doc/go1.21#windows), and this release updates esbuild from Go 1.20 to Go 1.22. Note that this only affects the binary esbuild executables that are published to the `esbuild` npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.21). That might look something like this: git clone https://github.com/evanw/esbuild.git cd esbuild go build ./cmd/esbuild ./esbuild.exe --version In addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's [release schedule](https://nodejs.org/en/about/previous-releases) for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the `esbuild-wasm` package and versions of node before node 17.4 (specifically the `crypto.getRandomValues` function). - Update `await using` behavior to match TypeScript TypeScript 5.5 subtly changes the way `await using` behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in [microsoft/TypeScript#58624](https://togithub.com/microsoft/TypeScript/pull/58624). - Allow `es2024` as a target environment The ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: <https://2ality.com/2024/06/ecmascript-2024.html>. The only addition that's relevant for esbuild is the regular expression `/v` flag. With `--target=es2024`, regular expressions that use the `/v` flag will now be passed through untransformed instead of being transformed into a call to `new RegExp`. - Publish binaries for OpenBSD on 64-bit ARM ([#​3665](https://togithub.com/evanw/esbuild/issues/3665), [#​3674](https://togithub.com/evanw/esbuild/pull/3674)) With this release, you should now be able to install the `esbuild` npm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip. This was contributed by [@​ikmckenz](https://togithub.com/ikmckenz). - Publish binaries for WASI (WebAssembly System Interface) preview 1 ([#​3300](https://togithub.com/evanw/esbuild/issues/3300), [#​3779](https://togithub.com/evanw/esbuild/pull/3779)) The upcoming WASI (WebAssembly System Interface) standard is going to be a way to run WebAssembly outside of a JavaScript host environment. In this scenario you only need a `.wasm` file without any supporting JavaScript code. Instead of JavaScript providing the APIs for the host environment, the WASI standard specifies a "system interface" that WebAssembly code can access directly (e.g. for file system access). Development versions of the WASI specification are being released using preview numbers. The people behind WASI are currently working on preview 2 but the Go compiler has [released support for preview 1](https://go.dev/blog/wasi), which from what I understand is now considered an unsupported legacy release. However, some people have requested that esbuild publish binary executables that support WASI preview 1 so they can experiment with them. This release publishes esbuild precompiled for WASI preview 1 to the `@esbuild/wasi-preview1` package on npm (specifically the file `@esbuild/wasi-preview1/esbuild.wasm`). This binary executable has not been tested and won't be officially supported, as it's for an old preview release of a specification that has since moved in another direction. If it works for you, great! If not, then you'll likely have to wait for the ecosystem to evolve before using esbuild with WASI. For example, it sounds like perhaps WASI preview 1 doesn't include support for opening network sockets so esbuild's local development server is unlikely to work with WASI preview 1. - Warn about `onResolve` plugins not setting a path ([#​3790](https://togithub.com/evanw/esbuild/issues/3790)) Plugins that return values from `onResolve` without resolving the path (i.e. without setting either `path` or `external: true`) will now cause a warning. This is because esbuild only uses return values from `onResolve` if it successfully resolves the path, and it's not good for invalid input to be silently ignored. - Add a new Go API for running the CLI with plugins ([#​3539](https://togithub.com/evanw/esbuild/pull/3539)) With esbuild's Go API, you can now call `cli.RunWithPlugins(args, plugins)` to pass an array of esbuild plugins to be used during the build process. This allows you to create a CLI that behaves similarly to esbuild's CLI but with additional Go plugins enabled. This was contributed by [@​edewit](https://togithub.com/edewit). </details> <details> <summary>dlclark/regexp2 (github.com/dlclark/regexp2)</summary> ### [`v1.11.2`](https://togithub.com/dlclark/regexp2/compare/v1.11.1...v1.11.2) [Compare Source](https://togithub.com/dlclark/regexp2/compare/v1.11.1...v1.11.2) ### [`v1.11.1`](https://togithub.com/dlclark/regexp2/compare/v1.11.0...v1.11.1) [Compare Source](https://togithub.com/dlclark/regexp2/compare/v1.11.0...v1.11.1) </details> <details> <summary>golang/go (go)</summary> ### [`v1.22.5`](https://togithub.com/golang/go/compare/go1.22.4...go1.22.5) </details> <details> <summary>watchexec/watchexec (watchexec)</summary> ### [`v2.1.2`](https://togithub.com/watchexec/watchexec/releases/tag/v2.1.2): CLI v2.1.2 - New feature: `--watch-file` ([#​849](https://togithub.com/watchexec/watchexec/issues/849)) - Fix: manpage entry in deb/rpm packagings </details> --- ### Configuration 📅 **Schedule**: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/alecthomas/chroma). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjEuOSIsInVwZGF0ZWRJblZlciI6IjM3LjQyNS4xIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbXX0=--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> |
||
oliverpool
|
e06b52822a
|
pygments2chroma: escape regex.words (#982)
Discovered while building on top of https://github.com/alecthomas/chroma/issues/877#issuecomment-1858982870 (by @miliog) The pygments "regex.words" should be escaped, since they may contain special regex chars (like `^` or `+`). |
||
wackbyte
|
76772513ea
|
feat(lexers/hare): add done keyword (#979)
Adds the `done` keyword described in [this blog post](https://harelang.org/blog/2024-04-01-introducing-for-each-loops-in-hare/) and introduced in [0.24.2-rc1](https://lists.sr.ht/~sircmpwn/hare-dev/%3CD2FVIMECX52X.2MYXMW7OG4UIK@cmpwn.com%3E). |
||
|
Aru Sahni
|
d1034f8fe1
|
Update the Materialize lexer (#978)
This introduces some additional keywords. I've also scripted this on our end hence the changes in formatting and encoding of certain characters in attribute values. This also includes: - Some tests - Updates to the README to call out the `--csrf-key` argument for chromad. Without it securecookie throws an error. |
||
Avi Herman
|
2d94bda8a5
|
added the nordic theme via chroma/styles/nordic.xml (#977)
I added the "Nordic" theme from [AlexvZyl's](https://github.com/AlexvZyl) project [nordic.nvim](https://github.com/AlexvZyl/nordic.nvim). All colors are cross referenced from the nordic theme and matches 95% of syntax highlighting exactly. Thanks! |
||
|
renovate[bot]
|
42005cfd38
|
chore(deps): update dependency python3 to v3.12.3 (#976)
[](https://renovatebot.com) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [python3](https://togithub.com/indygreg/python-build-standalone) | patch | `3.12.2` -> `3.12.3` | --- ### Configuration 📅 **Schedule**: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/alecthomas/chroma). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MTMuMiIsInVwZGF0ZWRJblZlciI6IjM3LjQxMy4yIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbXX0=--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> |
||
|
renovate[bot]
|
5d317d2fd4
|
chore(deps): update all non-major dependencies (#974) | ||
Joe Mooring
|
2060600780
|
styles: Fix Gleam alias (#973) | ||
|
renovate[bot]
|
b35d6a86c7
|
chore(deps): update all non-major dependencies (#955)
[](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---|---|---| | [esbuild](https://togithub.com/evanw/esbuild) | | minor | `0.20.2` -> `0.21.4` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [github.com/alecthomas/assert/v2](https://togithub.com/alecthomas/assert) | require | minor | `v2.7.0` -> `v2.10.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [github.com/alecthomas/chroma/v2](https://togithub.com/alecthomas/chroma) | require | minor | `v2.13.0` -> `v2.14.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [go](https://togithub.com/golang/go) | | patch | `1.22.1` -> `1.22.3` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [goreleaser](https://togithub.com/goreleaser/goreleaser) | | minor | `1.24.0` -> `1.26.2` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>evanw/esbuild (esbuild)</summary> ### [`v0.21.4`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0214) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.21.3...v0.21.4) - Update support for import assertions and import attributes in node ([#​3778](https://togithub.com/evanw/esbuild/issues/3778)) Import assertions (the `assert` keyword) have been removed from node starting in v22.0.0. So esbuild will now strip them and generate a warning with `--target=node22` or above: ▲ [WARNING] The "assert" keyword is not supported in the configured target environment ("node22") [assert-to-with] example.mjs:1:40: 1 │ import json from "esbuild/package.json" assert { type: "json" } │ ~~~~~~ ╵ with Did you mean to use "with" instead of "assert"? Import attributes (the `with` keyword) have been backported to node 18 starting in v18.20.0. So esbuild will no longer strip them with `--target=node18.N` if `N` is 20 or greater. - Fix `for await` transform when a label is present This release fixes a bug where the `for await` transform, which wraps the loop in a `try` statement, previously failed to also move the loop's label into the `try` statement. This bug only affects code that uses both of these features in combination. Here's an example of some affected code: ```js // Original code async function test() { outer: for await (const x of [Promise.resolve([0, 1])]) { for (const y of x) if (y) break outer throw 'fail' } } // Old output (with --target=es6) function test() { return __async(this, null, function* () { outer: try { for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) { const x = temp.value; for (const y of x) if (y) break outer; throw "fail"; } } catch (temp) { error = [temp]; } finally { try { more && (temp = iter.return) && (yield temp.call(iter)); } finally { if (error) throw error[0]; } } }); } // New output (with --target=es6) function test() { return __async(this, null, function* () { try { outer: for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) { const x = temp.value; for (const y of x) if (y) break outer; throw "fail"; } } catch (temp) { error = [temp]; } finally { try { more && (temp = iter.return) && (yield temp.call(iter)); } finally { if (error) throw error[0]; } } }); } ``` - Do additional constant folding after cross-module enum inlining ([#​3416](https://togithub.com/evanw/esbuild/issues/3416), [#​3425](https://togithub.com/evanw/esbuild/issues/3425)) This release adds a few more cases where esbuild does constant folding after cross-module enum inlining. ```ts // Original code: enum.ts export enum Platform { WINDOWS = 'windows', MACOS = 'macos', LINUX = 'linux', } // Original code: main.ts import { Platform } from './enum'; declare const PLATFORM: string; export function logPlatform() { if (PLATFORM == Platform.WINDOWS) console.log('Windows'); else if (PLATFORM == Platform.MACOS) console.log('macOS'); else if (PLATFORM == Platform.LINUX) console.log('Linux'); else console.log('Other'); } // Old output (with --bundle '--define:PLATFORM="macos"' --minify --format=esm) function n(){"windows"=="macos"?console.log("Windows"):"macos"=="macos"?console.log("macOS"):"linux"=="macos"?console.log("Linux"):console.log("Other")}export{n as logPlatform}; // New output (with --bundle '--define:PLATFORM="macos"' --minify --format=esm) function n(){console.log("macOS")}export{n as logPlatform}; ``` - Pass import attributes to on-resolve plugins ([#​3384](https://togithub.com/evanw/esbuild/issues/3384), [#​3639](https://togithub.com/evanw/esbuild/issues/3639), [#​3646](https://togithub.com/evanw/esbuild/issues/3646)) With this release, on-resolve plugins will now have access to the import attributes on the import via the `with` property of the arguments object. This mirrors the `with` property of the arguments object that's already passed to on-load plugins. In addition, you can now pass `with` to the `resolve()` API call which will then forward that value on to all relevant plugins. Here's an example of a plugin that can now be written: ```js const examplePlugin = { name: 'Example plugin', setup(build) { build.onResolve({ filter: /.*/ }, args => { if (args.with.type === 'external') return { external: true } }) } } require('esbuild').build({ stdin: { contents: ` import foo from "./foo" with { type: "external" } foo() `, }, bundle: true, format: 'esm', write: false, plugins: [examplePlugin], }).then(result => { console.log(result.outputFiles[0].text) }) ``` - Formatting support for the `@position-try` rule ([#​3773](https://togithub.com/evanw/esbuild/issues/3773)) Chrome shipped this new CSS at-rule in version 125 as part of the [CSS anchor positioning API](https://developer.chrome.com/blog/anchor-positioning-api). With this release, esbuild now knows to expect a declaration list inside of the `@position-try` body block and will format it appropriately. - Always allow internal string import and export aliases ([#​3343](https://togithub.com/evanw/esbuild/issues/3343)) Import and export names can be string literals in ES2022+. Previously esbuild forbid any usage of these aliases when the target was below ES2022. Starting with this release, esbuild will only forbid such usage when the alias would otherwise end up in output as a string literal. String literal aliases that are only used internally in the bundle and are "compiled away" are no longer errors. This makes it possible to use string literal aliases with esbuild's `inject` feature even when the target is earlier than ES2022. ### [`v0.21.3`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0213) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.21.2...v0.21.3) - Implement the decorator metadata proposal ([#​3760](https://togithub.com/evanw/esbuild/issues/3760)) This release implements the [decorator metadata proposal](https://togithub.com/tc39/proposal-decorator-metadata), which is a sub-proposal of the [decorators proposal](https://togithub.com/tc39/proposal-decorators). Microsoft shipped the decorators proposal in [TypeScript 5.0](https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#decorators) and the decorator metadata proposal in [TypeScript 5.2](https://devblogs.microsoft.com/typescript/announcing-typescript-5-2/#decorator-metadata), so it's important that esbuild also supports both of these features. Here's a quick example: ```js // Shim the "Symbol.metadata" symbol Symbol.metadata ??= Symbol('Symbol.metadata') const track = (_, context) => { (context.metadata.names ||= []).push(context.name) } class Foo { @​track foo = 1 @​track bar = 2 } // Prints ["foo", "bar"] console.log(Foo[Symbol.metadata].names) ``` **⚠️ WARNING ⚠️** This proposal has been marked as "stage 3" which means "recommended for implementation". However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification. - Fix bundled decorators in derived classes ([#​3768](https://togithub.com/evanw/esbuild/issues/3768)) In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix: ```js class Foo extends Object { @​(x => x) foo() { return Foo } } console.log(new Foo().foo()) ``` - Fix `tsconfig.json` files inside symlinked directories ([#​3767](https://togithub.com/evanw/esbuild/issues/3767)) This release fixes an issue with a scenario involving a `tsconfig.json` file that `extends` another file from within a symlinked directory that uses the `paths` feature. In that case, the implicit `baseURL` value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done for `tsconfig.json` because it's special-cased (the regular path resolver can't be used because the information inside `tsconfig.json` is involved in path resolution). Note that this fix no longer applies if the `--preserve-symlinks` setting is enabled. ### [`v0.21.2`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0212) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.21.1...v0.21.2) - Correct `this` in field and accessor decorators ([#​3761](https://togithub.com/evanw/esbuild/issues/3761)) This release changes the value of `this` in initializers for class field and accessor decorators from the module-level `this` value to the appropriate `this` value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change: ```js const dec = () => function() { this.bar = true } class Foo { @​dec static foo } console.log(Foo.bar) // Should be "true" ``` - Allow `es2023` as a target environment ([#​3762](https://togithub.com/evanw/esbuild/issues/3762)) TypeScript recently [added `es2023`](https://togithub.com/microsoft/TypeScript/pull/58140) as a compilation target, so esbuild now supports this too. There is no difference between a target of `es2022` and `es2023` as far as esbuild is concerned since the 2023 edition of JavaScript doesn't introduce any new syntax features. ### [`v0.21.1`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0211) - Fix a regression with `--keep-names` ([#​3756](https://togithub.com/evanw/esbuild/issues/3756)) The previous release introduced a regression with the `--keep-names` setting and object literals with `get`/`set` accessor methods, in which case the generated code contained syntax errors. This release fixes the regression: ```js // Original code x = { get y() {} } // Output from version 0.21.0 (with --keep-names) x = { get y: /* @​__PURE__ */ __name(function() { }, "y") }; // Output from this version (with --keep-names) x = { get y() { } }; ``` </details> <details> <summary>alecthomas/assert (github.com/alecthomas/assert/v2)</summary> ### [`v2.10.0`](https://togithub.com/alecthomas/assert/compare/v2.9.0...v2.10.0) [Compare Source](https://togithub.com/alecthomas/assert/compare/v2.9.0...v2.10.0) ### [`v2.9.0`](https://togithub.com/alecthomas/assert/compare/v2.8.1...v2.9.0) [Compare Source](https://togithub.com/alecthomas/assert/compare/v2.8.1...v2.9.0) ### [`v2.8.1`](https://togithub.com/alecthomas/assert/compare/v2.8.0...v2.8.1) [Compare Source](https://togithub.com/alecthomas/assert/compare/v2.8.0...v2.8.1) ### [`v2.8.0`](https://togithub.com/alecthomas/assert/compare/v2.7.0...v2.8.0) [Compare Source](https://togithub.com/alecthomas/assert/compare/v2.7.0...v2.8.0) </details> <details> <summary>alecthomas/chroma (github.com/alecthomas/chroma/v2)</summary> ### [`v2.14.0`](https://togithub.com/alecthomas/chroma/releases/tag/v2.14.0) [Compare Source](https://togithub.com/alecthomas/chroma/compare/v2.13.0...v2.14.0) #### Changelog - [`1e983e7`](https://togithub.com/alecthomas/chroma/commit/1e983e7) lexers/cue: support CUE attributes ([#​961](https://togithub.com/alecthomas/chroma/issues/961)) - [`9347b55`](https://togithub.com/alecthomas/chroma/commit/9347b55) Add Gleam syntax highlighting ([#​959](https://togithub.com/alecthomas/chroma/issues/959)) - [`6b7ffe1`](https://togithub.com/alecthomas/chroma/commit/6b7ffe1) chore(styles): add tokyonight inspired styles ([#​957](https://togithub.com/alecthomas/chroma/issues/957)) - [`736c0ea`](https://togithub.com/alecthomas/chroma/commit/736c0ea) Typescript: Several fixes ([#​952](https://togithub.com/alecthomas/chroma/issues/952)) - [`e5c25d0`](https://togithub.com/alecthomas/chroma/commit/e5c25d0) Org: Keep all newlines ([#​951](https://togithub.com/alecthomas/chroma/issues/951)) - [`d07caa4`](https://togithub.com/alecthomas/chroma/commit/d07caa4) chore(deps): update module github.com/alecthomas/assert/v2 to v2.7.0 ([#​949](https://togithub.com/alecthomas/chroma/issues/949)) - [`5f83664`](https://togithub.com/alecthomas/chroma/commit/5f83664) Vue: Handle more edge cases ([#​950](https://togithub.com/alecthomas/chroma/issues/950)) - [`32c053f`](https://togithub.com/alecthomas/chroma/commit/32c053f) chore(deps): update all non-major dependencies ([#​948](https://togithub.com/alecthomas/chroma/issues/948)) - [`2580aaa`](https://togithub.com/alecthomas/chroma/commit/2580aaa) Add Bazel bzlmod support into Python lexer ([#​947](https://togithub.com/alecthomas/chroma/issues/947)) </details> <details> <summary>golang/go (go)</summary> ### [`v1.22.3`](https://togithub.com/golang/go/compare/go1.22.2...go1.22.3) ### [`v1.22.2`](https://togithub.com/golang/go/compare/go1.22.1...go1.22.2) </details> <details> <summary>goreleaser/goreleaser (goreleaser)</summary> ### [`v1.26.2`](https://togithub.com/goreleaser/goreleaser/releases/tag/v1.26.2) #### Changelog ##### Bug fixes - [`b3d6460`]( |
||
|
renovate[bot]
|
4af3b82c6b
|
chore(deps): update dependency watchexec to v2 (#962)
[](https://renovatebot.com) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [watchexec](https://togithub.com/watchexec/watchexec) | major | `1.25.1` -> `2.1.1` | --- ### Release Notes <details> <summary>watchexec/watchexec (watchexec)</summary> ### [`v2.1.1`](https://togithub.com/watchexec/watchexec/releases/tag/v2.1.1): CLI v2.1.1 - Regression: `-w, --watch` was accidentally set to behave as `-W` ([#​828](https://togithub.com/watchexec/watchexec/issues/828)) ### [`v2.1.0`](https://togithub.com/watchexec/watchexec/releases/tag/v2.1.0): CLI v2.1.0 - New: `-W`, `--watch-non-recursive` for watching paths without also watching subfolders. - New: out-of-tree git repositories are now detected (i.e. when `.git` is a file rather than a folder) - Logs are also improved slightly with less nonsense at startup. ### [`v2.0.0`](https://togithub.com/watchexec/watchexec/releases/tag/v2.0.0): CLI v2.0.0 This is the first breaking release. Most of it is cleaning up a number of deprecated options, and changing some defaults. The idea, however, is to start a new era of Watchexec releases, where breaking changes are allowed more easily (to give an idea of how breaking-change-averse the project has been: this release was planned *in January 2022!* and ever-delayed since). Fear not! The cadence of breaking releases will be at most once or twice a year, and whenever possible a deprecation will precede a break by at least three months. Watchexec will remain a stable part of your workflow, while allowing ourselves some evolution. - Shell default changes to `$SHELL` when it is present. ([#​210](https://togithub.com/watchexec/watchexec/issues/210)) Use `--shell=sh` to switch back if your `$SHELL` is something else. - Shell default changes to Powershell on Windows when Watchexec detects it is running in Powershell. ([#​80](https://togithub.com/watchexec/watchexec/issues/80)) Use `--shell=cmd` to switch back to CMD.EXE, or set the `SHELL` environment variable. A reminder that Windows 7 is *not* supported, and hasn't been for years. - `--on-busy-update` defaults to `do-nothing` now (was `queue`). Events received while a command is running won't trigger a run of the command immediately following this one. - `-W` / `--watch-when-idle` is removed, as it is now the default. - The default for `--stop-timeout` is now 10 seconds. - `--debounce`, `--delay-run`, `--poll`, and `--stop-timeout` now prefer durations with a unit, and warn if given unit-less durations. The default units for these are millisecond for `--debounce` and `--poll`, and seconds for `--delay-run` and `--stop-timeout`, which is a source of confusion. Unit-less durations will be removed in a future breaking release. - `--no-shell` is removed. Use `--shell=none` instead. The `-n` short option remains as an alias to `--shell=none`. - `-k` / `--kill` is removed. Use `--signal=KILL` instead. - `--changes-only` is removed. Use `--print-events` instead. - `--emit-events-to` defaults to `none`, and the `environment` mode is deprecated. - `--emit-events-to` no longer accepts `stdin` (deprecated alias for `stdio`) and `json-stdin`(deprecated alias for `json-stdio`). - `--no-ignore` is removed. Use `--no-project-ignore` instead. - `--no-environment` is deprecated. - `--clear=reset` will reset the screen on graceful shutdown. ([#​797](https://togithub.com/watchexec/watchexec/issues/797)) - `--no-process-group` is deprecated. - Watchexec no longer warns (nor does anything else) when it sees the deprecated `WATCHEXEC_FILTERER` environment variable. #### Improvements - New: `--wrap-process=MODE` lets you choose between using process groups, process sessions, or nothing at all. ([#​794](https://togithub.com/watchexec/watchexec/issues/794)) - New: the `WATCHEXEC_TMPDIR` environment variable can be used to customize where Watchexec will write temporary files, if for some reason your `$TMPDIR` is unwritable. ([#​814](https://togithub.com/watchexec/watchexec/issues/814)) - Fix: watchexec no longer creates a temporary file at startup. ([#​814](https://togithub.com/watchexec/watchexec/issues/814)) - Fix: the screen is no longer cleared on all events, only when starting a new process. ([#​809](https://togithub.com/watchexec/watchexec/issues/809)) #### Experimental new feature As a treat, this release also features an experimental new option: `-j` or `--filter-prog`, which lets you write *filter programs*. ##### `-j`, `--filter-prog EXPRESSION` Provide your own custom filter programs in [jaq](https://togithub.com/01mf02/jaq#examples) (similar to jq) syntax. Programs are given an event in the same format as described in `--emit-events-to` and must return a boolean. In addition to the jaq stdlib, watchexec adds some custom filter definitions: - `path | file_meta` returns file metadata or null if the file does not exist. - `path | file_size` returns the size of the file at path, or null if it does not exist. - `path | file_read(bytes)` returns a string with the first n bytes of the file at path. If the file is smaller than n bytes, the whole file is returned. There is no filter to read the whole file at once to encourage limiting the amount of data read and processed. - `string | hash`, and `path | file_hash` return the hash of the string or file at path. No guarantee is made about the algorithm used: treat it as an opaque value. - `any | kv_store(key)`, `kv_fetch(key)`, and `kv_clear` provide a simple key-value store. Data is kept in memory only, there is no persistence. Consistency is not guaranteed. - `any | printout`, `any | printerr`, and `any | log(level)` will print or log any given value to stdout, stderr, or the log (levels = error, warn, info, debug, trace), and pass the value through (so `[1] | log("debug") | .[]` will produce a `1` and log `[1]`). All filtering done with such programs, and especially those using kv or filesystem access, is much slower than the other filtering methods. If filtering is too slow, events will back up and stall watchexec. Take care when designing your filters. If the argument to this option starts with an '@​', the rest of the argument is taken to be the path to a file containing a jaq program. Jaq programs are run in order, after all other filters, and short-circuit: if a filter (jaq or not) rejects an event, execution stops there, and no other filters are run. Additionally, they stop after outputting the first value, so you'll want to use 'any' or 'all' when iterating, otherwise only the first item will be processed, which can be quite confusing! ##### Examples: Regexp ignore filter on paths: ```jq all(.tags[] | select(.kind == "path"); .absolute | test("[.]test[.]js$")) | not ``` Pass any event that creates a file: ```jq any(.tags[] | select(.kind == "fs"); .simple == "create") ``` Pass events that touch executable files: ```jq any(.tags[] | select(.kind == "path" && .filetype == "file"); .absolute | metadata | .executable) ``` Ignore files that start with shebangs: ```jq any(.tags[] | select(.kind == "path" && .filetype == "file"); .absolute | read(2) == "#!") | not ``` More examples can be found and contributed in the [discussion thread](https://togithub.com/watchexec/watchexec/discussions/592) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/alecthomas/chroma). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4zMTMuMSIsInVwZGF0ZWRJblZlciI6IjM3LjMyMS4yIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbXX0=--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> |
||
|
renovate[bot]
|
e1ed1890f0
|
chore(deps): update dependency svu to v2 (#971)
[](https://renovatebot.com) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [svu](https://togithub.com/caarlos0/svu) | major | `1.12.0` -> `2.0.1` | --- ### Release Notes <details> <summary>caarlos0/svu (svu)</summary> ### [`v2.0.1`](https://togithub.com/caarlos0/svu/releases/tag/v2.0.1) This is just to prevent gomod caching issues when using it as a library. It is otherwise the same as v2.0.0, I had to recreate that tag due to a CI misconfiguration. #### Changelog ##### New Features - [`b58abe1`]( |
||
robin
|
6f1db96235
|
chore(styles): add evergarden inspired style (#970) | ||
Simran
|
d7cf9378e7
|
AQL: Add builtin functions introduced in v3.12 (#968)
New functions added to 3.12.0 (`PARSE_COLLECTION()`, `PARSE_KEY()`, `RANDOM()`, `REPEAT()`, `TO_CHAR()`) and the current stand for the upcoming 3.12.1 (`ENTRIES()`). Some functions were also removed (`CALL_GREENSPUN()`, `PREGEL_RESULT()`) but I think it makes sense to keep them in the definition so that highlighting older queries still works. |
||
Paul Jolly
|
1e983e734d
|
lexers/cue: support CUE attributes (#961)
Currently the following CUE results in the chroma lexer producing an
error token for the '@':
value: string @go(Value)
This code is, however, valid CUE. '@go' is an attributes.
This change adds lexer support for attributes in CUE.
v2.14.0
|
||
Pi-Cla
|
9347b550ab
|
Add Gleam syntax highlighting (#959)
Resolves #958 |
||
cloudbridgeuy
|
6b7ffe10ff
|
chore(styles): add tokyonight inspired styles (#957)
Add [`tokyonight`](https://github.com/folke/tokyonight.nvim) based styles. `tokyonight-storm`  `tokyonight-day`  `tokyonight-moon`  `tokyonight-night`  Co-authored-by: Guzmán Monné <guzmonne@hotmail.com> |
||
|
Gusted
|
736c0ea4cd
|
Typescript: Several fixes (#952) | ||
|
Gusted
|
e5c25d045e
|
Org: Keep all newlines (#951)
- Move the `*` operator to inside the capturing group so all characters that match `\s` is preserved and not just the first character. - Add tests. - Resolves https://github.com/alecthomas/chroma/issues/845 <details><summary>Input</summary> ```orgmode Generic text. /Italicized/ *strong* =Heading= ~Codeblock~ +StrikeTrough+ _Underlined_ ``` </details> ## Before  ## After  |
||
|
renovate[bot]
|
d07caa43c1
|
chore(deps): update module github.com/alecthomas/assert/v2 to v2.7.0 (#949)
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/alecthomas/assert/v2](https://togithub.com/alecthomas/assert) | `v2.6.0` -> `v2.7.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>alecthomas/assert (github.com/alecthomas/assert/v2)</summary> ### [`v2.7.0`](https://togithub.com/alecthomas/assert/compare/v2.6.0...v2.7.0) [Compare Source](https://togithub.com/alecthomas/assert/compare/v2.6.0...v2.7.0) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/alecthomas/chroma). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4yNjkuMiIsInVwZGF0ZWRJblZlciI6IjM3LjI2OS4yIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIn0=--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> |
||
|
Gusted
|
5f83664c2a
|
Vue: Handle more edge cases (#950)
- The parsing of `v-` directives expected that this always ended in `">`, however it is possible that there are other attributes after an `v-` directive also it made the assumption that there couldn't be any spaces in the value of the directive. Therefore it could result in incorrect lexing where almost the whole file could be marked as an LiteralString. - Handle `-` in HTML element names. - Explicitly mark `=` as an operator token. - Tests added. - Ref: https://codeberg.org/forgejo/forgejo/issues/2945 ## Before  ## After  |
||
|
renovate[bot]
|
32c053f501
|
chore(deps): update all non-major dependencies (#948)
[](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---|---|---| | [esbuild](https://togithub.com/evanw/esbuild) | | patch | `0.20.1` -> `0.20.2` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [github.com/alecthomas/chroma/v2](https://togithub.com/alecthomas/chroma) | require | minor | `v2.12.0` -> `v2.13.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>evanw/esbuild (esbuild)</summary> ### [`v0.20.2`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0202) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.20.1...v0.20.2) - Support TypeScript experimental decorators on `abstract` class fields ([#​3684](https://togithub.com/evanw/esbuild/issues/3684)) With this release, you can now use TypeScript experimental decorators on `abstract` class fields. This was silently compiled incorrectly in esbuild 0.19.7 and below, and was an error from esbuild 0.19.8 to esbuild 0.20.1. Code such as the following should now work correctly: ```ts // Original code const log = (x: any, y: string) => console.log(y) abstract class Foo { @​log abstract foo: string } new class extends Foo { foo = '' } // Old output (with --loader=ts --tsconfig-raw={\"compilerOptions\":{\"experimentalDecorators\":true}}) const log = (x, y) => console.log(y); class Foo { } new class extends Foo { foo = ""; }(); // New output (with --loader=ts --tsconfig-raw={\"compilerOptions\":{\"experimentalDecorators\":true}}) const log = (x, y) => console.log(y); class Foo { } __decorateClass([ log ], Foo.prototype, "foo", 2); new class extends Foo { foo = ""; }(); ``` - JSON loader now preserves `__proto__` properties ([#​3700](https://togithub.com/evanw/esbuild/issues/3700)) Copying JSON source code into a JavaScript file will change its meaning if a JSON object contains the `__proto__` key. A literal `__proto__` property in a JavaScript object literal sets the prototype of the object instead of adding a property named `__proto__`, while a literal `__proto__` property in a JSON object literal just adds a property named `__proto__`. With this release, esbuild will now work around this problem by converting JSON to JavaScript with a computed property key in this case: ```js // Original code import data from 'data:application/json,{"__proto__":{"fail":true}}' if (Object.getPrototypeOf(data)?.fail) throw 'fail' // Old output (with --bundle) (() => { // <data:application/json,{"__proto__":{"fail":true}}> var json_proto_fail_true_default = { __proto__: { fail: true } }; // entry.js if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail) throw "fail"; })(); // New output (with --bundle) (() => { // <data:application/json,{"__proto__":{"fail":true}}> var json_proto_fail_true_default = { ["__proto__"]: { fail: true } }; // example.mjs if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail) throw "fail"; })(); ``` - Improve dead code removal of `switch` statements ([#​3659](https://togithub.com/evanw/esbuild/issues/3659)) With this release, esbuild will now remove `switch` statements in branches when minifying if they are known to never be evaluated: ```js // Original code if (true) foo(); else switch (bar) { case 1: baz(); break } // Old output (with --minify) if(1)foo();else switch(bar){case 1:} // New output (with --minify) foo(); ``` - Empty enums should behave like an object literal ([#​3657](https://togithub.com/evanw/esbuild/issues/3657)) TypeScript allows you to create an empty enum and add properties to it at run time. While people usually use an empty object literal for this instead of a TypeScript enum, esbuild's enum transform didn't anticipate this use case and generated `undefined` instead of `{}` for an empty enum. With this release, you can now use an empty enum to generate an empty object literal. ```ts // Original code enum Foo {} // Old output (with --loader=ts) var Foo = /* @​__PURE__ */ ((Foo2) => { })(Foo || {}); // New output (with --loader=ts) var Foo = /* @​__PURE__ */ ((Foo2) => { return Foo2; })(Foo || {}); ``` - Handle Yarn Plug'n'Play edge case with `tsconfig.json` ([#​3698](https://togithub.com/evanw/esbuild/issues/3698)) Previously a `tsconfig.json` file that `extends` another file in a package with an `exports` map failed to work when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release. - Work around issues with Deno 1.31+ ([#​3682](https://togithub.com/evanw/esbuild/issues/3682)) Version 0.20.0 of esbuild changed how the esbuild child process is run in esbuild's API for Deno. Previously it used `Deno.run` but that API is being removed in favor of `Deno.Command`. As part of this change, esbuild is now calling the new `unref` function on esbuild's long-lived child process, which is supposed to allow Deno to exit when your code has finished running even though the child process is still around (previously you had to explicitly call esbuild's `stop()` function to terminate the child process for Deno to be able to exit). However, this introduced a problem for Deno's testing API which now fails some tests that use esbuild with `error: Promise resolution is still pending but the event loop has already resolved`. It's unclear to me why this is happening. The call to `unref` was recommended by someone on the Deno core team, and calling Node's equivalent `unref` API has been working fine for esbuild in Node for a long time. It could be that I'm using it incorrectly, or that there's some reference counting and/or garbage collection bug in Deno's internals, or that Deno's `unref` just works differently than Node's `unref`. In any case, it's not good for Deno tests that use esbuild to be failing. In this release, I am removing the call to `unref` to fix this issue. This means that you will now have to call esbuild's `stop()` function to allow Deno to exit, just like you did before esbuild version 0.20.0 when this regression was introduced. Note: This regression wasn't caught earlier because Deno doesn't seem to fail tests that have outstanding `setTimeout` calls, which esbuild's test harness was using to enforce a maximum test runtime. Adding a `setTimeout` was allowing esbuild's Deno tests to succeed. So this regression doesn't necessarily apply to all people using tests in Deno. </details> <details> <summary>alecthomas/chroma (github.com/alecthomas/chroma/v2)</summary> ### [`v2.13.0`](https://togithub.com/alecthomas/chroma/releases/tag/v2.13.0) [Compare Source](https://togithub.com/alecthomas/chroma/compare/v2.12.0...v2.13.0) ##### Changelog - [`bd47355`](https://togithub.com/alecthomas/chroma/commit/bd47355) fix: include compress state in style cache key - [`1235bbf`](https://togithub.com/alecthomas/chroma/commit/1235bbf) chore(deps): update all non-major dependencies ([#​944](https://togithub.com/alecthomas/chroma/issues/944)) - [`4e60c81`](https://togithub.com/alecthomas/chroma/commit/4e60c81) C#: Allow for empty comments ([#​943](https://togithub.com/alecthomas/chroma/issues/943)) - [`fe5dde8`](https://togithub.com/alecthomas/chroma/commit/fe5dde8) Add Lexer for NDISASM ([#​933](https://togithub.com/alecthomas/chroma/issues/933)) - [`6dd9f26`](https://togithub.com/alecthomas/chroma/commit/6dd9f26) feat: introduce a LRU compiled style cache for the HTML formatter ([#​938](https://togithub.com/alecthomas/chroma/issues/938)) - [`898d467`](https://togithub.com/alecthomas/chroma/commit/898d467) lexers/cue: support definitions and dollars in field names ([#​935](https://togithub.com/alecthomas/chroma/issues/935)) - [`0f92de4`](https://togithub.com/alecthomas/chroma/commit/0f92de4) chore(deps): update all non-major dependencies ([#​934](https://togithub.com/alecthomas/chroma/issues/934)) - [`381050b`](https://togithub.com/alecthomas/chroma/commit/381050b) Major updates to Caddyfile lexer ([#​932](https://togithub.com/alecthomas/chroma/issues/932)) - [`e9292e6`](https://togithub.com/alecthomas/chroma/commit/e9292e6) chore(deps): update dependency goreleaser to v1.24.0 ([#​925](https://togithub.com/alecthomas/chroma/issues/925)) - [`ddbae13`](https://togithub.com/alecthomas/chroma/commit/ddbae13) chore: upgrade Go - [`7ce2caf`](https://togithub.com/alecthomas/chroma/commit/7ce2caf) Fix lexers check when built with newer Go ([#​928](https://togithub.com/alecthomas/chroma/issues/928)) - [`506e36f`](https://togithub.com/alecthomas/chroma/commit/506e36f) fix(lexers/go): "~" is a valid token ([#​926](https://togithub.com/alecthomas/chroma/issues/926)) - [`f4788c0`](https://togithub.com/alecthomas/chroma/commit/f4788c0) docs: add import to README - [`39115eb`](https://togithub.com/alecthomas/chroma/commit/39115eb) chore(deps): update dependency esbuild to v0.20.0 ([#​921](https://togithub.com/alecthomas/chroma/issues/921)) - [`4c6fdb1`](https://togithub.com/alecthomas/chroma/commit/4c6fdb1) Add .avsc to JSON lexer ([#​920](https://togithub.com/alecthomas/chroma/issues/920)) - [`ee60f7e`](https://togithub.com/alecthomas/chroma/commit/ee60f7e) Add missing token types for Rego + add Rego to README ([#​919](https://togithub.com/alecthomas/chroma/issues/919)) - [`ae36e63`](https://togithub.com/alecthomas/chroma/commit/ae36e63) Add support for Rego syntax ([#​918](https://togithub.com/alecthomas/chroma/issues/918)) - [`d7a7dd3`](https://togithub.com/alecthomas/chroma/commit/d7a7dd3) chore(deps): update module github.com/alecthomas/assert/v2 to v2.5.0 ([#​917](https://togithub.com/alecthomas/chroma/issues/917)) - [`c31293c`](https://togithub.com/alecthomas/chroma/commit/c31293c) chore(deps): update dependency go to v1.21.6 ([#​915](https://togithub.com/alecthomas/chroma/issues/915)) - [`ebc34cf`](https://togithub.com/alecthomas/chroma/commit/ebc34cf) fix file extension typo, remove redundent parens ([#​914](https://togithub.com/alecthomas/chroma/issues/914)) - [`641b06f`](https://togithub.com/alecthomas/chroma/commit/641b06f) Fix type operators not being recognised in Haskell ([#​913](https://togithub.com/alecthomas/chroma/issues/913)) - [`3ef9475`](https://togithub.com/alecthomas/chroma/commit/3ef9475) chore(deps): update dependency watchexec to v1.25.1 ([#​912](https://togithub.com/alecthomas/chroma/issues/912)) - [`23368be`](https://togithub.com/alecthomas/chroma/commit/23368be) styles(catpuccin/gh-dark): LineHighlight grp ([#​911](https://togithub.com/alecthomas/chroma/issues/911)) - [`a8704a8`](https://togithub.com/alecthomas/chroma/commit/a8704a8) Add lexer for RPMSpec ([#​907](https://togithub.com/alecthomas/chroma/issues/907)) - [`eb47752`](https://togithub.com/alecthomas/chroma/commit/eb47752) Add lexer for Promela ([#​906](https://togithub.com/alecthomas/chroma/issues/906)) - [`3f395c9`](https://togithub.com/alecthomas/chroma/commit/3f395c9) chore(deps): update all non-major dependencies ([#​905](https://togithub.com/alecthomas/chroma/issues/905)) - [`2018c2f`](https://togithub.com/alecthomas/chroma/commit/2018c2f) chore(deps): update all non-major dependencies ([#​904](https://togithub.com/alecthomas/chroma/issues/904)) - [`016768b`](https://togithub.com/alecthomas/chroma/commit/016768b) Add desktop entry lexer ([#​903](https://togithub.com/alecthomas/chroma/issues/903)) - [`f130045`](https://togithub.com/alecthomas/chroma/commit/f130045) chore(deps): update dependency watchexec to v1.24.1 ([#​901](https://togithub.com/alecthomas/chroma/issues/901)) - [`9670d34`](https://togithub.com/alecthomas/chroma/commit/9670d34) chore(deps): update actions/checkout action to v4 ([#​899](https://togithub.com/alecthomas/chroma/issues/899)) - [`ad03817`](https://togithub.com/alecthomas/chroma/commit/ad03817) chore(deps): update all non-major dependencies ([#​898](https://togithub.com/alecthomas/chroma/issues/898)) - [`76039a5`](https://togithub.com/alecthomas/chroma/commit/76039a5) chore(deps): update all non-major dependencies ([#​897](https://togithub.com/alecthomas/chroma/issues/897)) - [`678b799`](https://togithub.com/alecthomas/chroma/commit/678b799) Add a lexer for the Materialize SQL dialect ([#​896](https://togithub.com/alecthomas/chroma/issues/896)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/alecthomas/chroma). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4yNDUuMCIsInVwZGF0ZWRJblZlciI6IjM3LjI0NS4wIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIn0=--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> |
||
farcop
|
2580aaaa8e
|
Add Bazel bzlmod support into Python lexer (#947)
https://bazel.build/concepts/build-ref "such a boundary marker file could be MODULE.bazel, REPO.bazel, or in legacy contexts, WORKSPACE or WORKSPACE.bazel." |
||
|
Alec Thomas
|
bd47355e46 |
fix: include compress state in style cache key
Fixes #945v2.13.0 |
||
|
renovate[bot]
|
1235bbf2ce
|
chore(deps): update all non-major dependencies (#944) | ||
Gusted
|
4e60c816eb
|
C#: Allow for empty comments (#943) | ||
Andrzej Lichnerowicz
|
fe5dde8cf4
|
Add Lexer for NDISASM (#933)
The Netwide Disassembler outputs text that is assembly prefixed with memory offsets and opcode bytes. |
||
|
Alec Thomas
|
6dd9f269ef
|
feat: introduce a LRU compiled style cache for the HTML formatter (#938)
```
🐚 ~/dev/chroma $ benchcmp before.txt after.txt
benchmark old ns/op new ns/op delta
BenchmarkHTMLFormatter-8 160560 77797 -51.55%
benchmark old allocs new allocs delta
BenchmarkHTMLFormatter-8 1267 459 -63.77%
benchmark old bytes new bytes delta
BenchmarkHTMLFormatter-8 52568 25067 -52.32%
```
|
||
|
Paul Jolly
|
898d467079
|
lexers/cue: support definitions and dollars in field names (#935)
'$' is valid in a bare field name in CUE. It is not special. It happens to be used by convention at the start of field names, but that is about it. Definitions start with '#'. Add a "section" of tests that cover the various types of field. There are no errors in new "tests", whereas before (i.e. without the change to the CUE lexer) there would have been. |
||
|
renovate[bot]
|
0f92de4f03
|
chore(deps): update all non-major dependencies (#934)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> |
||
Francis Lavoie
|
381050ba00
|
Major updates to Caddyfile lexer (#932)
* Major updates to Caddyfile lexer * yaml editorconfig * nolint false positive |
||
|
renovate[bot]
|
e9292e6994
|
chore(deps): update dependency goreleaser to v1.24.0 (#925)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> |
||
|
Alec Thomas
|
ddbae13883 | chore: upgrade Go | ||
W. Michael Petullo
|
7ce2caf57a
|
Fix lexers check when built with newer Go (#928)
Newer versions of Go emit '\f' rather than "\u000c" for formfeeds. This patch adjusts the expected values for the lexers tests to match. Fixes: https://github.com/alecthomas/chroma/issues/927 See also: https://github.com/golang/go/issues/64346 for the change to Go. Signed-off-by: W. Michael Petullo <mike@flyn.org> |
||
Abhinav Gupta
|
506e36f9e0
|
fix(lexers/go): "~" is a valid token (#926)
With the introduction of generics, tilde is a valid punctuation token in Go programs. https://go.dev/ref/spec#Operators_and_punctuation This updates the punctuation regex for the Go lexer, and adds a test to ensure that it's treated as such. |
||
|
Alec Thomas
|
f4788c0e9e | docs: add import to README | ||
|
renovate[bot]
|
39115ebe5c
|
chore(deps): update dependency esbuild to v0.20.0 (#921)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> |
