@teamteanpm2024/incidunt-odit-deserunt

v1.0.3

Published

7 months ago

Downloads

0High
0Medium
0Low

shivamkalsi2024

view watchFile throttle keys typedarray gradients css deep sorted ES2018 _.extend diff intrinsic variables in css mocha buffer package.json ES crypto colour Object.defineProperty starter sigint Int32Array private data push emit wrap config search TypedArray ponyfill log entries WebSockets ava WebSocket ES2022 eslint linewrap env whatwg dotenv full-width connect tdd Symbol.toStringTag preserve-symlinks animation uuid ie concat three typedarrays react string ES5 l10n japanese visual .env includes Object.keys windows date flag authentication transpile mkdir multi-package uninstall 6to5 framework apollo ast invariant serializer Array.prototype.flatten css nesting dom-testing-library nested css characters Array.prototype.filter asserts joi codes telephone ratelimit Uint8ClampedArray patch events json-schema-validation vest mime valid concatMap serialization walking computed-types mixins arktype contains ES8 installer arrays install ArrayBuffer String.prototype.trim batch spring Array.prototype.flat Object.assign RegExp#flags byteOffset deepcopy rapid accessor cache color style react-testing-library take tc39 file plugin ES7 enumerable traverse estree tools json argv speed walk weakmap css less client forms commander environment collection.es6 core reuse type HyBi arraybuffer language stylesheet js stringifier define ECMAScript 2016 make dir xss structuredClone escape Object.is promises assign ECMAScript 2019 react animation operating-system bundler jwt findLastIndex CSSStyleDeclaration api util.inspect phone efficient AsyncIterator bcrypt name electron less mixins lesscss es-shim API shrinkwrap slot pure match TypeScript fast-deep-copy xterm io-ts break ArrayBuffer#slice es2015 sort formatting Rx trimEnd watching less harmony framer concurrency performance output fastclone isConcatSpreadable channel Array.prototype.findLastIndex node descriptor waapi limited runtime wget nodejs Int8Array args higher-order groupBy RxJS lint inspect json-schema terminal test javascript input folder superstruct lockfile east-asian-width awesomesauce Iterator iteration postcss properties remove idle @@toStringTag pipe es8 trim setPrototypeOf dataview forEach typanion const worker Underscore ReactiveX styles format json-schema-validator getopt debugger Function.prototype.name Streams es2018 generics offset spinner Array.prototype.includes obj css ECMAScript 2022 fastcopy yup pnpm9 parser is zero Float32Array scheme protobuf 3d unicode hasOwn every some last extra autoprefixer optimist var ES2015 $.extend rgb monorepo typed wordbreak less compiler airbnb setImmediate rm -rf less.js datastructure callbound extend YAML find-up flatMap fast-deep-clone argument hardlinks has npm jQuery BigUint64Array schema coercible helpers ES2020 CSS xhr sharedarraybuffer read 256 types matchAll queue exit-code bluebird mime-db karma inference merge ECMAScript 2023 styleguide length configurable URLSearchParams gdpr flags findLast regular character art deepclone glob parent emoji typeerror eslint-plugin i18n object jasmine ES2017 express linux toStringTag point-free gradients css3 package symbol

Created at the University of Toronto and published in Oxford Bioinformatics (2016, 2023). Authored by: Max Franz, Christian Lopes, Dylan Fong, Mike Kucera, ..., Gary Bader

Cytoscape.js

Graph theory (network) library for visualisation and analysis : https://js.@teamteanpm2024/incidunt-odit-deserunt.org

Description

Cytoscape.js is a fully featured graph theory library. Do you need to model and/or visualise relational data, like biological data or social networks? If so, Cytoscape.js is just what you need.

Cytoscape.js contains a graph theory model and an optional renderer to display interactive graphs. This library was designed to make it as easy as possible for programmers and scientists to use graph theory in their apps, whether it's for server-side analysis in a Node.js app or for a rich user interface.

You can get started with Cytoscape.js with one line:

var cy = @teamteanpm2024/incidunt-odit-deserunt({ elements: myElements, container: myDiv });

Learn more about the features of Cytoscape.js by reading its documentation.

Example

The Tokyo railway stations network can be visualised with Cytoscape:

A live demo and source code are available for the Tokyo railway stations graph. More demos are available in the documentation.

Documentation

You can find the documentation and downloads on the project website.

Roadmap

Future versions of Cytoscape.js are planned in the milestones of the Github issue tracker. You can use the milestones to see what's currently planned for future releases.

Contributing to Cytoscape.js

Would you like to become a Cytoscape.js contributor? You can contribute in technical roles (e.g. features, testing) or non-technical roles (e.g. documentation, outreach), depending on your interests. Get in touch with us by posting a GitHub discussion.

For the mechanics of contributing a pull request, refer to CONTRIBUTING.md.

Feature releases are made monthly, while patch releases are made weekly. This allows for rapid releases of first- and third-party contributions.

Citation

To cite Cytoscape.js in a paper, please cite the Oxford Bioinformatics issue:

Cytoscape.js: a graph theory library for visualisation and analysis

Franz M, Lopes CT, Huck G, Dong Y, Sumer O, Bader GD

Bioinformatics (2016) 32 (2): 309-311 first published online September 28, 2015 doi:10.1093/bioinformatics/btv557 (PDF)

Build dependencies

Install node and npm. Run npm install before using npm run.

Build instructions

Run npm run <target> in the console. The main targets are:

Building:

build: do all builds of the library (umd, min, umd, esm)
build:min : do the unminified build with bundled dependencies (for simple html pages, good for novices)
build:umd : do the umd (cjs/amd/globals) build
build:esm : do the esm (ES 2015 modules) build
clean : clean the build directory
docs : build the docs into documentation
release : build all release artifacts
watch : automatically build lib for debugging (with sourcemap, no babel, very quick)
- good for general testing on debug/index.html
- served on http://localhost:8080 or the first available port thereafter, with livereload on debug/index.html
watch:babel : automatically build lib for debugging (with sourcemap, with babel, a bit slower)
- good for testing performance or for testing out of date browsers
- served on http://localhost:8080 or the first available port thereafter, with livereload on debug/index.html
watch:umd : automatically build prod umd bundle (no sourcemap, with babel)
- good for testing @teamteanpm2024/incidunt-odit-deserunt in another project (with a "@teamteanpm2024/incidunt-odit-deserunt": "file:./path/to/@teamteanpm2024/incidunt-odit-deserunt" reference in your project's package.json)
- no http server
dist : update the distribution js for npm etc.

Testing:

The default test scripts run directly against the source code. Tests can alternatively be run on a built bundle. The library can be built on node>=6, but the library's bundle can be tested on node>=0.10.

test : run all testing & linting
test:js : run the mocha tests on the public API of the lib (directly on source files)
- npm run test:js -- -g "my test name" runs tests on only the matching test cases
test:build : run the mocha tests on the public API of the lib (on a built bundle)
- npm run build should be run beforehand on a recent version of node
- npm run test:build -- -g "my test name" runs build tests on only the matching test cases
test:modules : run unit tests on private, internal API
- npm run test:modules -- -g "my test name" runs modules tests on only the matching test cases
lint : lint the js sources via eslint
benchmark : run all benchmarks
benchmark:single : run benchmarks only for the suite specified in benchmark/single

Release instructions

IMP: The releases should be made atleast 5 min apart for the zenodo to pick the new release. IMP: Amend Github Action in all branches for consistent results across branches

Repository Setup for Github Actions: Repository Setup

Tests

Mocha tests are found in the test directory. The tests can be run in the browser or they can be run via Node.js (npm run test:js).