This project was bootstrapped with Create React App.
In the project directory, you can run:
npm install (First time only, ignore security warnings)
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Lint the project
To fix linting errors, run npm run lint:fix
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify
The whole code in this repository is integrated as a submodule in GMOD's JBrowse-Components. We are currently stashing our code @https://github.com/graph-genome/jbrowse-components/tree/pangenome_group_testing.
In order to get the plugin in JBrowse-Web to run, execute the following steps:
Clone the JBrowse-Components repository:
git clone --recurse-submodules -b pangenome_group_testing [email protected]:graph-genome/jbrowse-components.git
Install dependencies:
cd jbrowse-components/
yarn
Start the development server (it takes some time until it is up...):
(cd packages/jbrowse-web/ && yarn start)
Navigate to File -> New pangenome view. Now you have a PangenomeView track running in JBrowse2!
All test files must be copied to jbrowse-components/packages/jbrowse-web/test_data.
In jbrowse-components/packages/pangenome-view/src/PangenomeView/components/prototype/src/PangenomeSchematic.js change path data to path test_data so that we point to the currect folder for our data to load.