should this template repo have a yarn.lock at all

[rbuels]

Given that this is a plugin template, should it have a yarn.lock?

I recently ran into a problem where the yarn lockfile was forcing @jbrowse/cli 1.5.0, which had a nonfunctional jbrowse create, which caused the run of yarn setup to fail.

Wonder if we should leave the yarn.lock out of the template, what do y'all think?

[rbuels]

I think I answered my own question with a "yes", because after 3fff082 I found that yarn browse no longer worked because the filenames that tsdx was producing in the dist/ folder changed and the served jbrowse could no longer find them. Fixed by b36805a