modeler_build_process

[Jean-Baptiste-Lasselle]

Excuse-me, jsut a bit annooyed here, about one thing :

• Ok, this is open source
• Ok, I have to guess things on my own
• But no, this :

    "app:auto-test": "npm run app:test -- --watch",
    "app:dev": "electron ./app/dev.js resources/diagram/simple.bpmn",
    "app:test": "nyc --reporter lcov --exclude \"app/test/**\" --exclude \"app/**/__tests__\" mocha --require ./app/test/expect \"app/**/*-spec.js\"",
    "client:build": "(cd client && npm run build)",
    "client:auto-test": "(cd client && npm run auto-test)",
    "client:dev": "(cd client && npm run dev)",
    "client:test": "(cd client && npm run test)",
    "all": "run-s clean lint test \"build -- {@}\" --",
    "auto-test": "run-p *:auto-test",
    "clean": "del-cli 'dist/*' app/public",
    "dev": "run-p \"app:dev -- {@}\" client:dev --",
    "build:distro": "node tasks/distro.js",
    "build:test-distro": "node tasks/test-distro.js",
    "build": "run-s client:build \"build:distro -- {@}\" \"build:test-distro -- {@}\" --",
    "lint": "eslint .",
    "postinstall": "lerna bootstrap",
    "prerelease": "run-s update-license-book",
    "update-license-book": "node tasks/license-book.js -o THIRD_PARTY_NOTICES -c",
    "send-license-book-summary": "node tasks/send-license-book-summary.js -s",
    "release": "lerna publish --force-publish",
    "test": "run-s *:test",
"start": "run-s \"dev -- {@}\" --"

Does not make a build process clear.

I just spent 2 hours trying to just start the BPMN Modeler, without whihc the BPMN engine (well you know )

Camunda is a process management software, and its referenced in Jenkow Jenkins plugin

I really can't uderstand how that team can think of that package.json pushing any clearly stated build process.

[Jean-Baptiste-Lasselle]

Excuse-me, jsut a bit annooyed here, about one thing :

• Ok, this is open source
• Ok, I have to guess things on my own
• But no, this :

    "app:auto-test": "npm run app:test -- --watch",
    "app:dev": "electron ./app/dev.js resources/diagram/simple.bpmn",
    "app:test": "nyc --reporter lcov --exclude \"app/test/**\" --exclude \"app/**/__tests__\" mocha --require ./app/test/expect \"app/**/*-spec.js\"",
    "client:build": "(cd client && npm run build)",
    "client:auto-test": "(cd client && npm run auto-test)",
    "client:dev": "(cd client && npm run dev)",
    "client:test": "(cd client && npm run test)",
    "all": "run-s clean lint test \"build -- {@}\" --",
    "auto-test": "run-p *:auto-test",
    "clean": "del-cli 'dist/*' app/public",
    "dev": "run-p \"app:dev -- {@}\" client:dev --",
    "build:distro": "node tasks/distro.js",
    "build:test-distro": "node tasks/test-distro.js",
    "build": "run-s client:build \"build:distro -- {@}\" \"build:test-distro -- {@}\" --",
    "lint": "eslint .",
    "postinstall": "lerna bootstrap",
    "prerelease": "run-s update-license-book",
    "update-license-book": "node tasks/license-book.js -o THIRD_PARTY_NOTICES -c",
    "send-license-book-summary": "node tasks/send-license-book-summary.js -s",
    "release": "lerna publish --force-publish",
    "test": "run-s *:test",
"start": "run-s \"dev -- {@}\" --"

Does not make a build process clear.

I just spent 2 hours trying to just start the BPMN Modeler, without whihc the BPMN engine (well you know )

Camunda is a process management software, and its referenced in Jenkow Jenkins plugin

I really can't uderstand how that team can think of that package.json pushing any clearly stated build process.

[Jean-Baptiste-Lasselle]

• Amélioration, dépilage erreurs de build :

npm install --save-dev cross-env
npm install --save-dev webpack
npm install --save-dev webpack-cli
npm audit fix
npm install --save-dev case-sensitive-paths-webpack-plugin
npm audit fix
npm install --save-dev copy-webpack-plugin
npm audit fix
npm install --save-dev license-webpack-plugin

npm install --save-dev babel-loader
npm audit fix
npm install --save-dev @babel/core
npm audit fix
npm install --save-dev @babel/plugin-syntax-dynamic-import
npm audit fix
npm install --save-dev @babel/plugin-proposal-class-properties

npm audit fix
# for new transitive resolutions to be automatically resolved, instead of finding them one after the other
npm install 

npm run build

[Jean-Baptiste-Lasselle]

Donc il s'agit d'une application Electron, le build process est extrêment mal docuementé,; la question reste de voir si je peux fair eun run de cette application dans mon contenur, et je pense qu'il existe des solutions, mais : Je peux faire un test à récupérer l'exécutable electron, dans le dist/, résultant du build electron dans le conteneur. (Alors, ça, en Electron, ce serait pas mal...)

L'alternative web, à voir si j'ai une complexité accrue pour le déploiement ensuite (oui, je pense que leur fameuse application Electron est là pour packager le fichier *.bpmn, et derrière balancer un war déployé dans le moteur camunda, un serveur java, là il semble qu'ilsoit packagé dans un Tomcat, dans le conteneur...) :

https://github.com/bpmn-io/bpmn.io