Colin Diesh
Colin Diesh
I didn't mean to auto-close this issue. I just merged that one thing with dontRedispatch I am trying to brainstorm, but i don't have too many concrete ideas. - browser...
if this is still happening let me know. it is random trivia, but in the time since this issue, gff-js was replaced with a new package gff-nostream (https://github.com/cmdcolin/gff-nostream) that is...
(closed for now due to issue triaging for now, but can reopen if still happening!)
this would technically set a minimum node version of around 18, so could be disruptive in other ways. might be that this is just left undone...
(as context: current node maximum is node 14 in last release...due to the node-sass stuff). newer node on main can use the "export NODE_OPTIONS=--openssl-legacy-provider" to run newer node if needed...
interesting. the verbose:true workaround isn't too bad! thanks for finding
@mdonnalley the "verbose:true" workaround doesn't seem to work for jest anymore. i think =4.0.26 stopped working
similar issue in bbi-js https://github.com/GMOD/bbi-js/issues/55
initial testing found at least one possible fail, possible patch with htscodecs PR here https://github.com/jkbonfield/htscodecs/pull/1
cc @jrobinso there was a fix for some CRAM 3.1 files in new cram-js release v3.0.7. at least one file from the hts-specs test ("level4.cram") was failing in previous cram-js...