aboutsummaryrefslogtreecommitdiff
path: root/japanese/kon2-14dot/(developers-only)
diff options
context:
space:
mode:
authorHiroki Tagato <tagattie@FreeBSD.org>2025-12-21 12:35:58 +0000
committerHiroki Tagato <tagattie@FreeBSD.org>2025-12-21 12:47:23 +0000
commit331eb8eae50d49c8e87954dd6668b8944428618a (patch)
treec9663aa73e228649f81ceed3d44150981d550f90 /japanese/kon2-14dot/(developers-only)
parentdfa272b3b1ce2cba6b49c90e76cd5f54d40eafee (diff)
Mk/Uses: Add electron.mk and companion scriptsHEADmain
electron.mk and companion scripts for making it easier to port Electron-based applications. The electron.mk addresses the following obstacles in porting: - Need to adapt to different node package managers used in a project (npm, yarn, and pnpm) Different package managers have different commands and options. With electron.mk, porters don't have to worry about those differences using USE_ELECTRON=npm feature. - Need to create an archive of necessary node modules and host the file somewhere online An Electron-based project usually needs to install node modules using "npm install" command during the build phase. We can't allow this because "npm install" involves network access. So we had to pre-generate an archive of necessary node modules and host it somewhere online. electron.mk eliminates the necessity by locally generating the archive of the node modules on-the-fly at a host building the port during the fetch phase. - Need to adapt to different package builders used (electron-builder, electron-packager, and electron-forge) Different package builders have different commands and options. With electron.mk, porters don't have to worry about those differences using USE_ELECTRON=build feature. PR: 291321 Reviewed by: arrowd Approved by: portmgr (implicit) Differential Revision: https://reviews.freebsd.org/D54005
Diffstat (limited to 'japanese/kon2-14dot/(developers-only)')
0 files changed, 0 insertions, 0 deletions