Development in ccNetViz
This is the pipeline you should follow to make changes to ccNetViz:
- Fork ccNetViz repository e.g. from HelikarLab
- . Start a server (such as Apache) with a path to the ccNetViz directory.
- Make changes to src/ tree.
- Run "$ npm update" to download needed packages.
- Build with "$ npm run build" on the ccNetViz root directory.
- Clear cache from browser if updates are not loading: e.g. in Chrome, go to settings->privacy->Clear Browsing Data->select only "Cache images and files" and click "Clear browsing data".
- Run a test page (e.g. anyone in examples/) at the browser to see the results.
- Commit changes to your fork and make a pull request e.g. on the repository you forked.
Notes:
- If the file tree does not get updated, there might be issues with the files you are trying to update. You can try: "$ ./node_modules/.bin/babel --presets=es2015 ./src//<the_new_file>.js" to get things working.
- You have to build the package (e.g. into dist/) to run new code, i.e. you cannot make changes to src/ tree and load them to the browser.
- E.g. in Chrome, it always reused the package from cache (ctrl+shift+r does not force it to reload recently built package), i.e. you have to clear the cache.