Problem building existing code with JointJS 4.2 (Angular 8)

[pfalcon64]

Introduction

I have an existing application that is working well with JointJS Plus 4.1 and my Angular 8 environment

I am trying to update to JointJS 4.2 and have run into the following issue that is not present in the previous release. Note: I updated both @joint/core and @joint/plus to the current releases, and the issue seems to be in CORE:

---

ERROR in ./node_modules/@joint/core/dist/joint.min.js 8:300209
Module parse failed: Unexpected token (8:300209)
File was processed with these loaders:

• ./node_modules/@angular-devkit/build-optimizer/src/build-optimizer/webpack-loader.js
  You may need an additional loader to handle the result of these loaders.

---

I am disappointed that a point release has resulted in a breaking change? Can you provide any guidance.

I've attached a small test app that I've been using for experimentation. My code compiles in v4.2, but I haven't been able to run it to verify if I made the correct changes for the Layers API (compared to what was in beta previously). Note: I have a version of this that contains all of the node modules (its about 80-MB zipped) if that helps.

test-template Reduced - 4.2.2 Trial.zip

Steps to reproduce

No response

Restrictions & Constraints

No response

Does your question relate to JointJS or JointJS+. Select both if applicable.

JointJS

[Geliogabalus]

Hello!

First of all, when using @joint/plus you don't need to specify @joint/core version in your package.json. Correct @joint/core is installed via npm as usual. Every @joint/plus version is expected to work with a particular @joint/core release so you can get unexpected errors in other case. So this part is redundant:

    "@joint/core": "^4.2.2",
    "@joint/plus": "file:joint-plus.tgz",

Regarding the current issue, when using '@joint/plus' the @joint/core library is taken from the path according to its package.json: dist/joint.min.js. And in your extra-webpack.config.js you are only transpiling .mjs files which omits joint.min.js. After fixing it by adding .js transpiling it works as expected:

     test: /\.(mjs|js)$/,

The issue itself is covered by '@babel/plugin-transform-class-properties' plugin which you are already using.

[pfalcon64]

Thank you. I added the core library manually as I was trying to see if it made a difference (it didn't), but hadn't changed it back.

I made the changes to extra-webpack.config.js and the code now compiles again. thank you!!

For others in the same boat, I also had to increase the --max-old-space-size Node setting - some combination of the update and my code needed the extra memory allocated when debugging.