Colin Diesh

I could re open but this was essentially just a design decision that was made when we chose web pack. I'll reopen for posterity. Again welcome to give it a...

Is there anything that is particularly problematic about running setup.sh with a dev build?

The current model (since 1.13.0) is that it automatically rebuilds jbrowse from the source code when ./setup.sh if you are using a dev build or a github clone. This is...

@laceysanderson you would not need to rebuild any data directories. There have not been any changes to jbrowse that affect backwards compatibility so it should not require any reloading or...

Possibly also copy the jbrowse.conf/jbrowse_conf.json if you use those global configs

Issue #1265 had a request for a similar type of bulk export that I thought I'd lump here, which is exporting the sequences from multiple features in a region >I...

we could consider this PR but please note that jbrowse running on the web is a static web app and many "vulnerabilities" that may be listed may not really apply....

Does look perhaps like an off by one. I guess that would be an issue with the perl code generating the histograms If you want to try and check out...

This is the perl code that handles histograms https://github.com/GMOD/jbrowse/blob/master/src/perl5/FeatureTrack.pm#L157-L249 It writes to files such as "data/tracks/yourtrack/hist-20-0.json"

You should be able to directly modify the file like this in your local installation without any additional compilation steps, just simple edit of the perl and re-run flatfile-to-json as...