chore(deps): update dependency @lezer/generator to v1.7.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@lezer/generator	1.1.0 -> 1.7.0

---

Release Notes

lezer-parser/generator (@​lezer/generator)

v1.7.0

Compare Source

Bug fixes

Include type declarations for the Rollup plugin.

Named or @export-ed specialized tokens are now available in the terms file.

New features

The generator now emits a warning when rules generate a lot of different variants (usually due to a combinatory explosion of ? and | operators).

v1.6.0

Compare Source

Bug fixes

Fix an issue where the generator could output invalid JavaScript when a specialization used a string that started with a number.

Adjust TypeScript output to compile with recent tsc versions. Add a test for zero-length node mounts

New features

Support an exportName option to the Rollup plugin.

v1.5.1

Compare Source

Bug fixes

Fix a quadratic complexity in state merging.

v1.5.0

Compare Source

Bug fixes

Fix a build issue that made the ES version of the Rollup plugin fail to load.

New features

The new typeScript option to buildParserFile (and --typeScript option to lezer-generator) makes the tool emit TypeScript code.

v1.4.2

Compare Source

Bug fixes

Fix a regression in the build process that caused the Rollup plugin to not be part of the npm package.

v1.4.1

Compare Source

Bug fixes

Make this package usable in TypeScript setups with node16/nodenext resolution.

v1.4.0

Compare Source

New features

BuildOptions.contextTracker now takes a function, so that the code that produces it has access to the term IDs.

v1.3.0

Compare Source

New features

The test utilities can now be imported as "@​lezer/generator/test".

v1.2.4

Compare Source

Bug fixes

Fix a bug where precedences specified for local tokens were not properly applied.

v1.2.3

Compare Source

Bug fixes

Make sure the Rollup plugin imports the rest of the library using a full file path.

Make --help show the correct executable name.

v1.2.2

Compare Source

Bug fixes

Make sure require isn't used as an identifier in generator output.

v1.2.1

Compare Source

Bug fixes

Fix an invalid optimization that sometimes led to incomplete token precedence tables, leading to incorrect tokenization.

v1.2.0

Compare Source

Bug fixes

Fix a bug where the error to use () to denote empty options in a choice expression was signalled even when that is what the input did.

New features

Grammars can now declare @local tokens blocks defining all the tokens that may appear in a set of state, and allowing @else tokens that match everything else.

v1.1.3

Compare Source

Bug fixes

Fix broken Rollup plugin due to a bad import.

v1.1.2

Compare Source

Bug fixes

Fix a bug where the _ notation in tokens would match only half of a surrogate pair.

Fix a bug that caused invalid tokenizer data to be generated for character ranges ending in \uffff.

v1.1.1

Compare Source

Bug fixes

Emit enough information about external specializers to make ParserConfig.specializers fixable.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[cr-gpt]

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables for this repo. you could follow readme for more information

[pr-codex]

Tldr

Updated dependencies for @lezer/common, @lezer/generator, and @lezer/lr in the eo and phi packages.

Detailed summary

• Updated @lezer/common from version 1.0.0 to 1.0.2 in the eo and phi packages
• Updated @lezer/generator from version 1.1.0 to 1.2.2 in the eo and phi packages
• Updated @lezer/lr from version 1.2.0 to 1.3.3 in the eo and phi packages
• Updated dependencies in package-lock.json files for eo and phi packages

[yegor256]

@rultor please, try to merge

[rultor]

@rultor please, try to merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

[rultor]

@rultor please, try to merge

@renovate[bot] @yegor256 Oops, I failed. You can see the full log here (spent 12s)

+ set -e
+ set -o pipefail
++ dirname ./run.sh
+ cd .
+ echo 619326
+ echo '1.74.7 b768e876f'
1.74.7 b768e876f
+ date
Thu 06 Apr 2023 12:33:56 AM CEST
+ uptime
 00:33:56 up 133 days,  5:12,  0 users,  load average: 1.32, 1.16, 0.52
+ cat
com.rultor.spi.Profile: There is no 'merge' section in .rultor.yml for branch main in repo objectionary/try-phi
	at com.rultor.agents.req.StartsRequest.docker(StartsRequest.java:350)
	at com.rultor.agents.req.StartsRequest.vars(StartsRequest.java:255)
	at com.rultor.agents.req.StartsRequest.script(StartsRequest.java:148)
	at com.rultor.agents.req.StartsRequest.process(StartsRequest.java:109)
	at com.rultor.agents.AbstractAgent.execute(AbstractAgent.java:70)
	at com.rultor.spi.Agent.execute(Agent.java:84)
	at com.rultor.Routine.process(Routine.java:202)
	at com.rultor.Routine.unsafe_aroundBody0(Routine.java:180)
	at com.rultor.Routine.run(Routine.java:1)
	at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:179)
	at com.jcabi.aspects.aj.MethodInterrupter.wrap(MethodInterrupter.java:108)
	at com.rultor.Routine.unsafe(Routine.java:175)
	at com.rultor.Routine.run(Routine.java:142)
	at com.jcabi.log.VerboseRunnable.run(VerboseRunnable.java:190)
	at com.jcabi.aspects.aj.MethodScheduler.lambda./run.sh(MethodScheduler.java:194)
	at java.base/java.util.concurrent.Executors.call(Executors.java:539)
	at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor.run(ScheduledThreadPoolExecutor.java:305)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor.run(ThreadPoolExecutor.java:635)
	at com.jcabi.log.VerboseThreads.run(VerboseThreads.java:222)
	at java.base/java.lang.Thread.run(Thread.java:833)

+ exit -1
'cid' file is absent, most probably the Docker container wasn't started correctly