You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is a placeholder for my own feedback as I walk through this template to make my first jbrowse plugin. I come from the PHP/Tripal world so have a very beginner perspective.
it would be good to mention the format you want the licence in. It should indicate SPDX and provide a site to lookup other options.
when asking if we want it private or not, it should mention this indicates whether it shows up on NPM and that it does not impact whether it's on the JBrowse plugin listing.
Note: when running yarn you currently see the following warnings:
This issue is a placeholder for my own feedback as I walk through this template to make my first jbrowse plugin. I come from the PHP/Tripal world so have a very beginner perspective.
It would be very helpful to include a dockerfile to help people get started! Here's my current stab at this in my plugin: https://github.com/tripal/Tripal-JBrowse-InternetAccountPlugin/blob/main/Dockerfile
When filling out the repository prompting,
Note: when running
yarn
you currently see the following warnings:As a non-react developer it's not clear that I need to run
build
aftersetup
since setup also mentions that itadds a build of JBrowse 2
.When I try to serve the site, I get an error and it opens on port 9000.
Seeing the red deprecation made me think something was really wrong but apparently it's fine.
It wasn't clear to me that I needed to run both
yarn start
andyarn browse
and that I should see my jbrowse in http://localhost:8999.I am working on doing everything in a dockerfile and having both commands is problematic in that case. Instead I added a new
yarn startbrowse
command that could be my docker container entrypoint. You can see that here: https://github.com/tripal/Tripal-JBrowse-InternetAccountPlugin/blob/main/package.json#L39The text was updated successfully, but these errors were encountered: