[PR #2287] [CLOSED] chore(deps): bump @lezer/lr from 0.15.8 to 0.16.2 #3710

New issue

Closed

opened 2026-03-17 01:17:57 +03:00 by kerem · 0 comments

kerem commented

2026-03-17 01:17:57 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/hoppscotch/hoppscotch/pull/2287
Author: @dependabot[bot]
Created: 4/25/2022
Status: ❌ Closed

Base: main ← Head: dependabot/npm_and_yarn/lezer/lr-0.16.2

📝 Commits (1)

690ce84 chore(deps): bump @lezer/lr from 0.15.8 to 0.16.2

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 packages/codemirror-lang-graphql/package.json (+1 -1)

📄 Description

Bumps @lezer/lr from 0.15.8 to 0.16.2.

Changelog

Sourced from @lezer/lr's changelog.

0.16.2 (2022-04-21)

Bug fixes

Fix an issue that could make the parser merge adjacent error nodes even when they had different parent nodes.

0.16.1 (2022-04-21)

Bug fixes

Fix an issue that caused error nodes created for inserted tokens to sometimes end up in the wrong parent node.

0.16.0 (2022-04-20)

Bug fixes

Avoid the need for generated parser files to directly import @lezer/common.

Commits

a0ae934 Mark version 0.16.2
5e98e0c Don't merge error nodes across parent node boundaries
a3c6582 Mark version 0.16.1
e9312e0 Make sure error nodes created for insertion end up in the right parent
7719dfa Mark version 0.16.0
d3be7fb Bump serialized parser format version
323d6fa Allow strings as prop values in serialized parsers
74b14c6 Add hasWrappers
8ad4a23 Drop an outdated fixme
4c4d528 Support a propSources property on parser specs
Additional commits viewable in compare view

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 commands and options

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 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)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/hoppscotch/hoppscotch/pull/2287 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 4/25/2022 **Status:** ❌ Closed **Base:** `main` ← **Head:** `dependabot/npm_and_yarn/lezer/lr-0.16.2` --- ### 📝 Commits (1) - [`690ce84`](https://github.com/hoppscotch/hoppscotch/commit/690ce84922f37f8981f8bdec9e53a56ef347d4e9) chore(deps): bump @lezer/lr from 0.15.8 to 0.16.2 ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `packages/codemirror-lang-graphql/package.json` (+1 -1) </details> ### 📄 Description Bumps [@lezer/lr](https://github.com/lezer-parser/lr) from 0.15.8 to 0.16.2. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/lezer-parser/lr/blob/main/CHANGELOG.md"><code>@lezer/lr</code>'s changelog</a>.</em></p> <blockquote> <h2>0.16.2 (2022-04-21)</h2> <h3>Bug fixes</h3> <p>Fix an issue that could make the parser merge adjacent error nodes even when they had different parent nodes.</p> <h2>0.16.1 (2022-04-21)</h2> <h3>Bug fixes</h3> <p>Fix an issue that caused error nodes created for inserted tokens to sometimes end up in the wrong parent node.</p> <h2>0.16.0 (2022-04-20)</h2> <h3>Bug fixes</h3> <p>Avoid the need for generated parser files to directly import <code>@lezer/common</code>.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lezer-parser/lr/commit/a0ae934455b14338ddee700dee6e1ed985c5c0da"><code>a0ae934</code></a> Mark version 0.16.2</li> <li><a href="https://github.com/lezer-parser/lr/commit/5e98e0c0857c75d65da4ab01e784bd8f1e1e45f1"><code>5e98e0c</code></a> Don't merge error nodes across parent node boundaries</li> <li><a href="https://github.com/lezer-parser/lr/commit/a3c65822ffa93204db4e42ede9bcce488b1e5f52"><code>a3c6582</code></a> Mark version 0.16.1</li> <li><a href="https://github.com/lezer-parser/lr/commit/e9312e0b7174821fc473036e545fc36c8cbea315"><code>e9312e0</code></a> Make sure error nodes created for insertion end up in the right parent</li> <li><a href="https://github.com/lezer-parser/lr/commit/7719dfa00e402f52fc146ea7772bf420e3d5713b"><code>7719dfa</code></a> Mark version 0.16.0</li> <li><a href="https://github.com/lezer-parser/lr/commit/d3be7fb06778e6f7e6d044af5eacc2e5770e1c36"><code>d3be7fb</code></a> Bump serialized parser format version</li> <li><a href="https://github.com/lezer-parser/lr/commit/323d6faf66838111c5ac905dd4730ca6e6fe84c5"><code>323d6fa</code></a> Allow strings as prop values in serialized parsers</li> <li><a href="https://github.com/lezer-parser/lr/commit/74b14c6a35f52c114f7c3a27aef5110e19a46e0f"><code>74b14c6</code></a> Add hasWrappers</li> <li><a href="https://github.com/lezer-parser/lr/commit/8ad4a23ff5335e67b275e14027055264c7ead14c"><code>8ad4a23</code></a> Drop an outdated fixme</li> <li><a href="https://github.com/lezer-parser/lr/commit/4c4d5285a3bcf6f63e6606b26317b1ac010b7c26"><code>4c4d528</code></a> Support a propSources property on parser specs</li> <li>Additional commits viewable in <a href="https://github.com/lezer-parser/lr/compare/0.15.8...0.16.2">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@lezer/lr&package-manager=npm_and_yarn&previous-version=0.15.8&new-version=0.16.2)](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 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> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>