Some things that either seemed unclear in documentation:

lastTouchY is called lastTouchX

/**
 * Variable: lastTouchX
 *
 * Holds the y-coordinate of the last touch event for double tap detection.
 */
mxGraph.prototype.lastTouchY = 0;

"mxSelectionModel" should be "mxGraphSelectionModel"?

/**
 * Function: setSelectionModel
 * 
 * Sets the <mxSelectionModel> that contains the selection.
 */
mxGraph.prototype.setSelectionModel = function(selectionModel)
{
	this.selectionModel = selectionModel;
};

mxGraph.prototype.isConnectable takes argument

/**
 * Function: isConnectable
 * 
 * Returns true if the <connectionHandler> is enabled.
 */
mxGraph.prototype.isConnectable = function(connectable)
{
	return this.connectionHandler.isEnabled();
};

Does mxGraph.prototype.isExtendParentsOnAdd take an argument?

/**
 * Function: isExtendParentsOnAdd
 * 
 * Returns <extendParentsOnAdd>.
 */
mxGraph.prototype.isExtendParentsOnAdd = function(cell)
{
	return this.extendParentsOnAdd;
};

source, target and directed missing descriptions

/**
 * Function: getEdgesBetween
 * 
 * Returns the edges between the given source and target. This takes into
 * account collapsed and invisible cells and returns the connected edges
 * as displayed on the screen.
 * 
 * Parameters:
 * 
 * source -
 * target -
 * directed -
 */
mxGraph.prototype.getEdgesBetween = function(source, target, directed)
{
	directed = (directed != null) ? directed : false;
	var edges = this.getEdges(source);
	var result = [];

The current package published to NPM is seriously broken.

Based on your publishing script, what you are publishing to NPM here is the full mxgraph distribution. That is all source code, all build files, all resources in all languages. Additionally the package.json incorrectly contains webpack, grunt etc. as dependencies instead of devDependencies. Thus installing just the mxgraph package as a dependency in a newly created empty folder results in a total of 92 MB of files.

The package.json further defines "main": "./javascript/dist/build.js" to be the entry point of the package. The dist folder is however excluded through the .gitignore file. Thus the mxgraph library actually cannot be included from npm in its current form - the package is broken. The github repository recently received a .npmignore file (https://github.com/jgraph/mxgraph/commit/78a73184b0fd0fcb138bc8ba425d47047282faa6) which mitigates this issue, this is however not in the bitbucket repository yet (although referenced in the deploy script).

Your build script actually also pushes the js code to a separate mxgraph-js repository. This looks a bit more like what an npm package should contain but is also incompatible with npm usage. In order to be compatible with your documentation, the main file should include the UMD loader code you add during the grunt build process. Nevertheless it is of course a cleaner solution to directly publish to npm from the original code.

In order to fix these issues I created a fork with a single additional commit on bitbucket: https://bitbucket.org/lgleim/mxgraph2

Unfortunately I cannot create pull requests there and the github repo has a somewhat different structure.

Since I am not familiar with all the other requirements to be fulfilled in order to execute the build.sh script, I was not able to test the code with your build script. The build does complete successfully with the following steps:

git clone [email protected]:lgleim/mxgraph2.git
cd mxgraph2
sed "s/@VERSION@/3.9.2/" etc/build/mxgraph-package.json > package.json
npm install
# npm publish

So I kindly ask you to review and manually merge my patch and (hopefully) to subsequently publish a working version of mxgraph to the npm registry.

npm install of mxgraph 3.7.3 fails during 'grunt build' in the postinstall. The error output is shown below.

The problem is that in the 3.7.3 release the javascript shipped under javascript/src/js is one big mxClient.js file instead of the individual files used in previous releases. The postinstall script runs grunt build which loads Gruntfile.js and tries to merge all of the javascript files into one file (dist/build.js) with a factory function to load it and export it . Line 14 of Gruntfile.js looks for the mxClient.include pattern in javascript/src/js/mxClient.js but doesn't find any and then tries to call map on undefined because the regular expression does not match anything.

My workaround for now is to stick with version 3.7.2-2 as my code relies on the factory that the grunt build wraps around the mxgraph javscript.

> [email protected] postinstall c:\dev\mx\mxweb\node_modules\mxgraph
> grunt build

Loading "Gruntfile.js" tasks...ERROR
>> TypeError: Cannot read property 'map' of null
Warning: Task "build" not found. Use --force to continue.

Aborted due to warnings.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\
fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":
"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 3
npm ERR! [email protected] postinstall: `grunt build`
npm ERR! Exit status 3
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:

Currently I try to work with pretty big amount of objects in mxgraph, like rendering 10000 shapes at once. In that case there lots of problems with rendering cells. Each cell updated in a sequence, which leads to hanging browser. It would be great to use something like Cork / Uncork in nodejs. I will call something like mxgraph.stopUpdate(), add lots of elements, loadXML etc. and mxgraph.resumeUpdate() after finishing massive changes. Unfortunately I can't find methods to control update behavior in mxgraph in documentation.

Don't know why but when I do npm install mxgraph I'm unable to import "mxgraph"

import {
    mxClient,
    mxGraph,
    mxRubberband,
    mxUtils,
    mxEvent
} from "mxgraph";

But the npm install mxgraph-js everything works fine (aside from the fact that this one is an outdated fork)

Is anybody having issues with the npm install ? I'm currently trying to use it in a react project.

Apparently, any scroll in a page causes an offset for mouse events in the graph, making nearly impossible to use (in particular, creating new connections) when scrolled down the page. I was able to reproduce this behaviour in the example Helloport when making the browser window small enough to allow scrolling:

Offset in mouse events problem when page is scrolled

Working correctly when scroll is at the top of the page

I found this problem in Google Chrome and Firefox.

Moving and resizing components seems to be working fine.

Fixes #83 and #102 provided individual source files javascript/src/js are present instead of a single minified mxClient.js file when publishing to npm, also allows an npm install directly from the source.

I am using macOS Sierra 10.12.6, with node 8.4.0 and npm 5.3.0, when installing mxgraph using:

$npm -S install mxgraph

I get the following error:

npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue

> [email protected] install /Users/Nigel/git/mxtest/public/js/node_modules/fsevents
> node install

[fsevents] Success: "/Users/Nigel/git/mxtest/public/js/node_modules/fsevents/lib/binding/Release/node-v57-darwin-x64/fse.node" already installed
Pass --update-binary to reinstall or --build-from-source to recompile

> [email protected] postinstall /Users/Nigel/git/mxtest/public/js/node_modules/mxgraph
> grunt build

Loading "Gruntfile.js" tasks...ERROR
>> TypeError: Cannot read property 'map' of null
Warning: Task "build" not found. Use --force to continue.

Aborted due to warnings.
npm ERR! code ELIFECYCLE
npm ERR! errno 3
npm ERR! [email protected] postinstall: `grunt build`
npm ERR! Exit status 3
npm ERR! 
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/Nigel/.npm/_logs/2017-09-07T00_20_45_100Z-debug.log

I have attached the associated log file too. Nb: I changed the .log to .txt to enable the upload.

2017-09-07T00_20_45_100Z-debug.txt

the follow code to load mxgraph, but mxBasePath not working:

import factory from 'mxgraph';
const mx = factory({
      mxBasePath: 'assets',
});

if set window.mxBasePath = 'assets' is working well.

this demo can reappear the issues: https://stackblitz.com/edit/js-yjyqmw

version: 4.2.0

For now, you can use this package: https://www.npmjs.com/package/@epicfaace/mxgraph

But I'd like mxgraph to publish their latest version on the official npm repository.

In mxGraph 3.9.8 it is still not possible to install it via npm install.

The file "main": "./javascript/dist/build.js", described in package.json doesn't exist in the uploaded npm package.

WIth that issue an import is impossible within the browser

import {
  mxGraph,
  mxUtils,
  mxStencilRegistry,
  mxConstants,
  mxStencil,
  mxGraphModel,
} from 'mxgraph';

throws an error that mxgraph is undefined