Skip to main content
Version: 4.1

Frequently asked questions

Advanced installation scenarios​

Can I install JointJS+ using an NPM registry?​

Currently, there is no plan to publish JointJS+ to NPM, but you can host your own private NPM registry and serve JointJS+ from there.

Troubleshooting​

Why can't I see any JointJS content when I open a JointJS application?​

An error may have been encountered while loading JointJS - see below.

Why do I only see a blank page when I open a JointJS application?​

An error may have been encountered while loading your application. This problem can have several causes.

Resolution steps...
  • Look into your browser's console for any error messages.

    How can I open my browser's console?
    • Google Chrome: View > Developer > JavaScript Console
    • Safari: Develop > Show JavaScript Console
    • Edge: Tools > Developer > JavaScript Console
    • Firefox: Tools > Browser Tools > Web Developer Tools > Console
  • See below on this page if you can find a matching error message and follow its resolution steps.

  • If you cannot resolve the issue on your own, reach out to us on one of our support channels.

Uncaught ReferenceError: joint is not defined​

If you are using JointJS locally (e.g. you have downloaded it from GitHub), then this error may happen when you try to open a JointJS demo without first having followed the steps to set up JointJS.

Resolution steps...
  • Follow the directions in JointJS's README.md file (i.e. run yarn install and yarn run dist in the root folder of your local JointJS project).

  • Come back to the demo and try running it again.

info

Some demos have their own README.md files which specify additional setup steps. If you try opening such a demo without first having followed these additional steps, you will encounter another kind of error - see below.

Failed to load resource: net::ERR_FILE_NOT_FOUND for bundle.js​

This is the Chrome / Edge version of the missing file error for bundle.js - see below.

Loading failed for the script with source for bundle.js​

This is the Safari version of the missing file error for bundle.js - see below.

Not allowed to load local resource for bundle.js​

This is the Firefox version of the missing file error for bundle.js - see below.

Why is a JointJS demo complaining about missing bundle.js file?​

This error may happen when you try to open a JointJS / JointJS+ demo's index.html file without first having followed the demo's additional setup steps.

Resolution steps...
info

These steps assume that you have followed the steps to set up JointJS - see above.

  • Follow the directions in the demo's README.md file (usually, run npm install and npm start in the demo's folder).

  • Try opening the demo in your browser again.

Uncaught TypeError: Cannot read properties of undefined (reading 'Parser')​

This error may happen when you try to open the JointJS+ apps/Visio/DefaultImport demo's index.html file without first having followed the demo's additional setup steps - see below.

Uncaught TypeError: Cannot read properties of undefined (reading 'fromURL')​

This error may happen when you try to open the JointJS+ apps/Visio/DefaultImport demo's index.html file directly without first having followed the demo's additional setup steps.

Resolution steps...
  • Follow the directions in the demo's README.md file (i.e. run npm install and npm start in the demo's folder).

  • Try opening the demo in your browser again.

Stay in the know

Be where thousands of diagramming enthusiasts meet

Star us on GitHub