Tags: marioalop/vis-network
Tags
feat(build): add index files to bundles (visjs#223) This allows more visually appealing imports when used with bundlers: ```typescript // Old, but still works: import * as vis from "vis-network/standalone/esm/vis-network"; // New, achieving the same result (ESM): import * as vis from "vis-network/standalone"; // ESM explicitly: import * as vis from "vis-network/standalone/esm"; // UMD explicitly: import * as vis from "vis-network/standalone/umd"; ``` This partially works in HTML but the old way is preferred (less requests, library name in dev tools and better compatibility): ```html <!-- Old, still works. Recommended. --> <script type="text/javascript" src="https://unpkg.com/vis-network/standalone/umd/vis-network.min.js" ></script> <!-- New, works but has issues. Not recommended. --> <script type="module" src="https://unpkg.com/vis-network/standalone/esm" ></script> <!-- New, doesn't work. --> <script type="text/javascript" src="https://unpkg.com/vis-network/standalone/umd" ></script> ```
feat(deps): update, pin and fix (visjs#184) The dependencies got messed up (probably when I was merging upstream/master into peer-build). This adds missing dependencies, pins all the versions (Greenkeeper will inform us about outdated deps from now on) and updates all the outdated ones.
feat(build): add standalone and peer builds (visjs#85) * feat(build): add standalone and peer builds * chore(dist): update * style: reformat new files * fix(build): update to core-js 3 Also ditches rollup-plugin-babel-minify in favor of directly configuring babel plugin as the former doesn't work with core-js 3. * fix(build): make it actually work without errors * chore(dist): update * chore(package): fix clean script It missed all the new vis-network.* files. Now it deletes them. * fix(build): use folder structure instead of big mess * chore(types): remove useless d.ts file I have no idea why I put it there, it's not imported from anywhere. * fix(build): fix image copying and watch * chore(examples): use standalone build * chore(examples): add standalone/peer build examples * fix(build): get rid of default import from util Every UMD package overwrites the default and breaks everything. This will work as long as no two packages use the same name for one of their exports (seems to be the case right now). * fix(build): don't reexport data and util from peer DataSet, utils etc. can't be reexported because that would cause stack overflow in UMD builds. They all export vis namespace therefore reexporting leads to loading vis to load vis to load vis… * chore(dist): update * fix(build): update d.ts files for recent changes * chore(examples): fix script and style paths * style: reformat * chore(examples): add code examples to basic usage * chore(examples): add new builds examples to the index * chore(examples): add legacy build example * chore(examples): fix URL errors * docs: update how to * docs: fix typo * fix(build): don't capitalize nonconstructor objects * docs: update Gephi and DOT exports * chore(dist): update * chore(build): transpile dependencies This ensures that all dependencies match our browser list. * chore(dist): update * chore(build): don't ignore declarations * chore(dist): update * chore(build): use concat instead of flatMap This greatly increases compatibility as Array.prototype.flatMap is quite new and only recently supported by Node. * chore(build): add styles to files * chore(scripts): clean all generated files
fix(manipulation): use interaction to handle drag (visjs#175) Formelly manipulation system reimplemented dragging instead of using interaction to handle it. This resulted to interaction options being ignored during edge editing and adding. Forwarding the events to interaction handler solves these issues. Closes visjs#174.
PreviousNext