Miro Spönemann

The initial version was contributed to [open-vsx.org](https://open-vsx.org) via [open-vsx/publish-extensions](https://github.com/open-vsx/publish-extensions), that's a script that publishes a list of selected extensions every night. The extension was removed from the list because the...

See also #526 about normalizing relative paths.

Our current DI solution is more restrictive than Guice / Inversify, but it's also type-safe, which is great. > Creating a new service in that case is a bit too...

This will be considerably easier to implement with #438 and #440.

Debugging the .ts files of the hello-world project works fine. It's just the langium library files that are not correctly mapped. Isn't the `outFiles` setting just for the local project?

See discussion in https://github.com/langium/langium/pull/543#discussion_r901457437

Proposal: add a validation to mark such alternatives with different types as error. We can relax this when we see a use case where it's really necessary, but until then...

My proposal is to mark `x+=(ID | NUMBER)` with an error if `ID` and `NUMBER` have different types (string and number). You can simply solve this by introducing a _data...

> Would it be okay? I would personally prefer an array of strings over mixed strings and numbers, so yes I think the restriction should be ok. This is related...

A big challenge here is that the generated npm package pulls langium and langium-cli from the npm registry, but its contents may be already using new API from the next...