@jahmezz
Nothing here yet.
Nothing here yet.
No blogs yet.
And as I'm sure a lot of this post worked in past versions of these packages, here is my dependency list with their versions. "devDependencies": { "@electron-forge/cli": "^6.1.1", "@electron-forge/maker-deb": "^6.1.1", "@electron-forge/maker-rpm": "^6.1.1", "@electron-forge/maker-squirrel": "^6.1.1", "@electron-forge/maker-zip": "^6.1.1", "@electron-forge/plugin-webpack": "^6.1.1", "@typescript-eslint/eslint-plugin": "^5.59.1", "@typescript-eslint/parser": "^5.59.1", "@vercel/webpack-asset-relocator-loader": "^1.7.3", "css-loader": "^6.7.3", "electron": "24.1.3", "eslint": "^8.39.0", "eslint-plugin-import": "^2.27.5", "fork-ts-checker-webpack-plugin": "^7.3.0", "node-loader": "^2.0.0", "style-loader": "^3.3.2", "ts-loader": "^9.4.2", "ts-node": "^10.9.1", "typescript": "~4.5.4" }, "dependencies": { "axios": "^1.4.0", "electron-squirrel-startup": "^1.0.0", "tree-kill": "^1.2.2" }
Thank you. This clarified a lot of things. Noticed a few issues working through this... First, the setup npx command seems to be "webpack-typescript", not typescript-webpack. Flipping it causes an error. In addition, the virtualenv command also seemed to break on my Windows environment. There was some "setuptools" issue. What worked was python -m venv edtwExampleEnv Moving the Part 2 issues to Part 2.
After a bit of fiddling around, I got everything to work in Part 2 and I'll share the issues I found and resolved here. #1: The src/build/afterExtract.js python copy folder function doesn't seem to work. Update: This is a pathing issue it seems. The source folder should have the additional \edtwExample\ to reach the actual dist folder. Your Github repo adds a parent folder with .bat files which makes the existing path invalid. #2: I found other pathing issues that make it not work right out of the box. For example, the edtwExample.spec in the python folder points to edtwExample\manage.py, but the manage.py is in the same folder as the spec file. #3: The spawn command for production doesn't seem to run properly. I got a number of issues, but the approach I write here in "Edit" works. Edit: The previous way didn't work all the time. Here is a guaranteed way. const serverPath = path.join(app.getAppPath(),"..","..","python", "edtwExample.exe") const command = "${serverPath}" runserver --noreload ; return spawn(command, { shell: true, }); You need a stable path to work from. spawn on Node.js is based on the path your command line is calling processes from. I used app.getAppPath().