-
-
Notifications
You must be signed in to change notification settings - Fork 505
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vite-plugin unable to make/package #3658
Comments
In my case the error was saying
So run the following command to remove the link
This is my temp fix until the package gets updated to account for soft links on macOS if you get the same error but for a different package, just replace "markdown" with the package name e.g. "semver", "loose-envify" |
Pre-flight checklist
Electron Forge version
7.4.0
Electron version
31.2.1
Operating system
macOS 14.5
Last known working Electron Forge version
No response
Expected behavior
Able to package and make via electron forge cli on macOS using DMG @electron-forge/maker-dmg": "^7.4.0",
Actual behavior
So I created a new project using the template.
npm init electron-app@latest my-new-app -- --template=vite-typescript
This uses the latest template of 7.4.0, building and running works fine. I then add some packages that seem to cause this behavior.
I run
yarn make
it fails, so I enable debugging viaexport DEBUG=electrion-*
Run it again and get the following
Steps to reproduce
create new project
npm init electron-app@latest my-new-app -- --template=vite-typescript
add dmg maker
yarn add @electron-forge/maker-dmg
edit forge.config.ts replace zip maker with DMG maker
makers: [ new MakerSquirrel({}), new MakerDMG(), new MakerRpm({}), new MakerDeb({}), ],
add this dependency
yarn add @atlaskit/editor-common
make the project
yarn make
Additional information
Seems to be related to this issue
electron/asar#308
however I checked my yarn.lock file and see that @electron/asar points to version 3.2.10 which should be the version that fixed the possible symlink issue.
The text was updated successfully, but these errors were encountered: