KDL 2.0 compliance

[zkat]

KDL 2.0.0-draft.3 is now generally available (kdl-org/kdl#286), and with it, we've decided to encourage existing implementations to start working towards 2.0 support and send feedback and suggestions for anything you might run into, so I'm making this tracking issue. :)

[larsgw]

Chevrotain v11 (the parser lib) is ESM-only now, how do you feel about moving to ESM (or async import()) vs keeping it at v10 for now?

[larsgw]

There don't seem to be a great deal of other changes since v10 so I'd be fine with keeping that for now. https://chevrotain.io/docs/changes/CHANGELOG.html

[zkat]

I am, in general, in favor of ESM-ification, tbh. But if there's no big changes worth pulling in, compat is probably a better idea.

[larsgw]

Currently considering whether to just test for the DLCPs before parsing, or including them in the lexer (and complicating the token patterns in the process).

[dezren39]

KDL 2.0.0 is now released. :-) It would be great if this library got an update because then we could update the playground. (https://kdl-play.danini.dev/)

[larsgw]

@dezren39 working on it now (#24). Note that https://kdl-play.danini.dev/ uses a different JS library for KDL, namely https://github.com/bgotink/kdl

[zkat]

@dezren39 @larsgw there’s an “official” playground now at https://kdl.dev/play that runs KDL v2

[larsgw]

I am not sure what the appeal of this library over https://github.com/bgotink/kdl would be anymore.

[larsgw]

@zkat okay, it supports the tests now, and I've converted it to ESM.

[zkat]

I am not sure what the appeal of this library over https://github.com/bgotink/kdl would be anymore.

@larsgw idk. It's simpler, perhaps lighter/faster? And also in general I think it's good to have more options tbh.