I maintain WebAssembly port of oniguruma called onigasm which is, and preferably should remain, 1:1 API compatible with node-oniguruma.
Certain circumstances now require OnigScanner's ability to use regex syntaxes/flavours other than default oniguruma syntax.
Now, of course that change doesn't need to be part of node-oniguruma right now, but if only node-oniguruma and onigasm could sync up on the new spec that'd be super cool.
Current API as of [email protected]
OnigScanner(patterns: string[])
OnigRegExp(pattern: string)
Proposed API (whenever `node-oniguruma decides to get on board)
type OnigOptions = {
syntax: 'perl' | 'java' | 'ruby' | 'grep' | 'posix'
}
OnigScanner(patterns: string[], options?: OnigOptions)
OnigRegExp(pattern: string, options?: OnigOptions)
I maintain
WebAssemblyport ofonigurumacalledonigasmwhich is, and preferably should remain, 1:1 API compatible withnode-oniguruma.Certain circumstances now require
OnigScanner's ability to use regex syntaxes/flavours other than default oniguruma syntax.Now, of course that change doesn't need to be part of
node-onigurumaright now, but if onlynode-onigurumaandonigasmcould sync up on the new spec that'd be super cool.