Please tell me how to create an electron-builder development environment in a Windows.

Hi. I would like to small contribute to this project. I read this document and tried to create a development environment. But, I’m failing the “pnpm compile” command. There are some points to be worried about.

1. When I execute the pnpm install command, I get the error. ERR_PNPM_PREPARE_PKG_FAILURE not found: yarn.
2. When I execute the yalk link *** command, I get many warning messages. Could not find package `app-builder-lib` in store (C:\Users\***\AppData\Local\Yalc\packages\app-builder-lib), skipping.
3. When I execute the pnpm compile command, I get the error. ```‘tsc’ is not recognized as an internal or external command ~~~``

Any information is welcome.

[mmaietta]

Would you be willing to open a PR on the document with the information you needed to get your env set up? We can iterate on it from there 😃 It’s been a long time since I’ve had to set up an env and both my dev machines are already configured.

Doc: https://github.com/electron-userland/electron-builder/blob/master/CONTRIBUTING.md

[KaminoRyo]

The pnpm install and pnpm compile commands were successful with the yarn installed.🎊 A different installation log was displayed.

node_modules/.pnpm/esbuild@0.12.29/node_modules/esbuild: Running postinstall script, done in 3.8s node_modules/.pnpm/puppeteer@2.1.1/node_modules/puppeteer: Running install script, done in 14.9s

dependencies:

• dmg-license 1.0.11

devDependencies:

• @babel/plugin-transform-modules-commonjs 7.15.4
• @changesets/changelog-github 0.4.2
• @changesets/cli 2.19.0
• @milahu/patch-package-with-pnpm-support 6.4.8
• @types/node 16.7.10
• @typescript-eslint/eslint-plugin 4.33.0
• @typescript-eslint/parser 4.33.0
• conventional-changelog-cli 2.1.1
• dmd 6.0.0
• eslint 7.30.0
• eslint-config-prettier 8.3.0
• eslint-plugin-prettier 3.4.0
• fs-extra 10.0.0
• husky 7.0.1
• jest-cli 27.0.6
• jsdoc-to-markdown 7.0.1
• lint-staged 11.1.2
• markdown2html-pro 1.0.6
• path-sort 0.1.0
• prettier 2.3.2
• replace-in-file 6.2.0
• source-map-support 0.5.19
• ts-jsdoc 3.2.2
• typescript 4.3.5
• typescript-json-schema 0.51.0
• v8-compile-cache 2.3.0

. postinstall$ patch-package │ Applying patches… │ @changesets/cli@2.19.0 ✔ . prepare$ husky install

Next, Not in the specified order, but after pnpm compile , yalc publish <12 packages I need to link> in the packages folder. (This command cannot specify multiple packages, so you need to do it 12 times 😫) In this state, when yalc link <12 packages I need to link> is performed in the project folder (electron-builder), the following log is displayed.

Because of pnpm-workspace.yaml exists in this package --pure option will be used by default, to override use --no-pure. electron-forge-maker-appimage@23.0.8 added to .yalc\electron-forge-maker-appimage purely Because of pnpm-workspace.yaml exists in this package --pure option will be used by default, to override use --no-pure. electron-forge-maker-nsis@23.0.8 added to .yalc\electron-forge-maker-nsis purely Because of pnpm-workspace.yaml exists in this package --pure option will be used by default, to override use --no-pure. electron-forge-maker-nsis-web@23.0.8 added to .yalc\electron-forge-maker-nsis-web purely Because of pnpm-workspace.yaml exists in this package --pure option will be used by default, to override use --no-pure. electron-forge-maker-snap@23.0.8 added to .yalc\electron-forge-maker-snap purely Because of pnpm-workspace.yaml exists in this package --pure option will be used by default, to override use --no-pure. electron-builder@23.0.8 added to .yalc\electron-builder purely Because of pnpm-workspace.yaml exists in this package --pure option will be used by default, to override use --no-pure. builder-util@23.0.8 added to .yalc\builder-util purely Because of pnpm-workspace.yaml exists in this package --pure option will be used by default, to override use --no-pure. builder-util-runtime@9.0.2 added to .yalc\builder-util-runtime purely Because of pnpm-workspace.yaml exists in this package --pure option will be used by default, to override use --no-pure. electron-publish@23.0.8 added to .yalc\electron-publish purely Because of pnpm-workspace.yaml exists in this package --pure option will be used by default, to override use --no-pure. electron-builder-squirrel-windows@23.0.8 added to .yalc\electron-builder-squirrel-windows purely Because of pnpm-workspace.yaml exists in this package --pure option will be used by default, to override use --no-pure. dmg-builder@23.0.8 added to .yalc\dmg-builder purely Because of pnpm-workspace.yaml exists in this package --pure option will be used by default, to override use --no-pure. electron-updater@5.0.3 added to .yalc\electron-updater purely Because of pnpm-workspace.yaml exists in this package --pure option will be used by default, to override use --no-pure. app-builder-lib@23.0.8 added to .yalc\app-builder-lib purely

It’s not accurate because I don’t have any knowledge about workspace, but I think this is okay. That’s all for today.