You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After I build all of the shared packages, I go to build the electron app for production, but it fails with this:
⨯ /Users/notes-app/packages/database/.env must be under /Users/notes-app/apps/electron/ failedTask=build stackTrace=Error: /Users/notes-app/packages/database/.env must be under /Users/notes-app/apps/electron/
I am building the database package via rollup with this: "build": "rollup -c --bundleConfigAsCjs --environment INCLUDE_DEPS,BUILD:production",
I am building the electron app with this: "build:mac": "electron-vite build && electron-builder --mac",
How can I get this to work? Do I need to have a shared .env file at the root of the monorepo? Or do I need to build the database package a different way somehow that includes the env variables?
To reproduce
Run yarn run electron:build:mac
Environment
System: OS macOS 14.6.1
Additional context
No response
The text was updated successfully, but these errors were encountered:
Self-service
Describe the bug
I have a monorepo created using yarn workspaces where I have this structure.
The electron app has the database package as a dependency. And the database package has its own
.env
file.After I build all of the shared packages, I go to build the electron app for production, but it fails with this:
I am building the database package via rollup with this:
"build": "rollup -c --bundleConfigAsCjs --environment INCLUDE_DEPS,BUILD:production",
I am building the electron app with this:
"build:mac": "electron-vite build && electron-builder --mac",
How can I get this to work? Do I need to have a shared
.env
file at the root of the monorepo? Or do I need to build the database package a different way somehow that includes the env variables?To reproduce
Run
yarn run electron:build:mac
Environment
Additional context
No response
The text was updated successfully, but these errors were encountered: