# Generator throws error on docs example

**URL:** <https://discuss.codemirror.net/t/generator-throws-error-on-docs-example/5008>\
**Category:** Lezer\
**Created:** [September 14, 2022, 1:09pm UTC](https://discuss.codemirror.net/t/generator-throws-error-on-docs-example/5008 "2022-09-14T13:09:08Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![autay27](https://discuss.codemirror.net/user_avatar/discuss.codemirror.net/autay27/32/2474_2.png) [@autay27](https://discuss.codemirror.net/u/autay27)\
**Post date:** [September 14, 2022, 1:09pm UTC](https://discuss.codemirror.net/t/generator-throws-error-on-docs-example/5008/1 "2022-09-14T13:09:08Z")

</div>

I installed the lezer packages, made a language.grammar file and pasted the example grammar given in the docs:

```auto
@top Program { expression }

expression { Name | Number | BinaryExpression }

BinaryExpression { "(" expression ("+" | "-") expression ")" }

@tokens {
  Name { @asciiLetter+ }
  Number { @digit+ }
}

```

Then I tried to generate it from the command line with `npx @lezer/generator --names language.grammar`. But I get the following error:

```auto
Unexpected token '@asciiLetter' (language.grammar 8:9)

```

I don’t understand this since I didn’t change the code at all and the docs clearly state that @asciiLetter is a built in character set. What am I missing? Thanks for your help!

---

<div class="post-metadata">

**Author:** ![marijn](https://discuss.codemirror.net/user_avatar/discuss.codemirror.net/marijn/32/136_2.png) [@marijn](https://discuss.codemirror.net/u/marijn)\
**Post date:** [September 14, 2022, 1:50pm UTC](https://discuss.codemirror.net/t/generator-throws-error-on-docs-example/5008/2 "2022-09-14T13:50:36Z")

</div>

Could it be you’re using an older version of lezer-generator? That syntax (`@asciiLetter`) was introduced in 1.1.0.

---

<div class="post-metadata">

**Author:** ![autay27](https://discuss.codemirror.net/user_avatar/discuss.codemirror.net/autay27/32/2474_2.png) [@autay27](https://discuss.codemirror.net/u/autay27)\
**Post date:** [September 15, 2022, 12:22pm UTC](https://discuss.codemirror.net/t/generator-throws-error-on-docs-example/5008/3 "2022-09-15T12:22:38Z")

</div>

OK, I checked the versions. I had two packages installed via npm, `@lezer/generator` (1.1.1) and `lezer-generator` (0.13.4) both of which were up to date.

I tried uninstalling `lezer-generator` since I read that it’s an old version of `@lezer/generator` and maybe it was interfering. Afterwards, calling `npx @lezer/generator` results in the error `lezer-generator: not found`.

I guess I’m calling the tool incorrectly? Or is npm installing the wrong version?

---

<div class="post-metadata">

**Author:** ![marijn](https://discuss.codemirror.net/user_avatar/discuss.codemirror.net/marijn/32/136_2.png) [@marijn](https://discuss.codemirror.net/u/marijn)\
**Post date:** [September 15, 2022, 1:09pm UTC](https://discuss.codemirror.net/t/generator-throws-error-on-docs-example/5008/4 "2022-09-15T13:09:49Z")

</div>

@lezer/generator does provide the binary `lezer-generator`. It’s possible that npm messed up and, on deleting the old lezer-generator package, just removed the binary link. Reinstalling dependencies should help there.

---

<div class="post-metadata">

**Author:** ![autay27](https://discuss.codemirror.net/user_avatar/discuss.codemirror.net/autay27/32/2474_2.png) [@autay27](https://discuss.codemirror.net/u/autay27)\
**Post date:** [September 15, 2022, 1:48pm UTC](https://discuss.codemirror.net/t/generator-throws-error-on-docs-example/5008/5 "2022-09-15T13:48:55Z")

</div>

That worked! Thanks so much for your help. Seems like the problem was just me being a npm noob.

---

<div class="post-metadata">

**Author:** ![marijn](https://discuss.codemirror.net/user_avatar/discuss.codemirror.net/marijn/32/136_2.png) [@marijn](https://discuss.codemirror.net/u/marijn)\
**Post date:** [September 15, 2022, 2:05pm UTC](https://discuss.codemirror.net/t/generator-throws-error-on-docs-example/5008/6 "2022-09-15T14:05:11Z")

</div>

> [@autay27](#):
>
> Seems like the problem was just me being a npm noob.

Nah, this is more about npm being a buggy mess, I’d argue.
