1computer1 / lexure Goto Github PK

Allow multiple values in an option, e.g. --foo 1 --foo 2 --foo 3 would give 'foo' => ['1', '2', '3'] in the result,

Many parsing methods return null rather than throwing. I think throwing an error is nicer to write code for as a user and is closer to what Node.js does (ex. new URL('invalid') throws). Here I've rewritten the basic example from the readme the way it would be if it no longer returned null:

const input = '!hello world "cool stuff" --foo --bar=baz a b c';
const lexer = new lexure.Lexer(input)
    .setQuotes([
        ['"', '"'],
        ['“', '”']
    ]);

try {
    const res = lexer.lexCommand(s => s.startsWith('!') ? 1 : null);

    console.log(res);
} catch (error) {
    console.error('Bad input:', error);
}

If Lexure is having an error parsing that should be reflected in the code. This also has the added benefit of making return types cleaner since there's no more Whatever | null.
Interesting in hearing your thoughts on this.

Right now, longStrategy and longShortStrategy are hardcoded to use the usual -- and = syntax.
It would be nice to support more styles, such as --flag: or \flag by allowing users to pass in their own prefix and separator.
Current way to do this is to simply copy paste those strategies and modify the regex.

Basically, an Args#singleFromEnd that would retrieve from the end.
This way, users can express "last n arguments" or similar.

Issue

The following error pops up when trying to use the module:

Error: File 'node_modules/lexure/dist/types/index.d.ts' is not a module.

Reproduction

Install lexure (I used yarn add lexure, which installed [email protected]).

import { Lexer, Parser, Tokens, Unordered } from 'lexure';

Results in the error shown above.