Where can I find electron forge config js file where package.json is parsed?
I'm looking to use environment variables to store my apple user credentials, but the issue is with Electron Forge this is added to the package.json file which doesn't accept those variables. I'm looking for the .js file that parses the package.json file so I can replace the values with process.env variables.
I found the osxNotarize JS file but it takes the arguments from another module and while I THINK I could just insert them there, I don't want to break any of the logic that comes before or after that. I'd rather just get to the earliest point that the .json file is parsed and insert my variables there.
Any help is much appreciated!
It would be crazy to modify the Electron forge source, you should rather extract the electron forge configuration in a separate JS file : ElectronForge configuration and load your environment variables using process.env.YOUR_VARIABLE_NAME
- How to configure package.json to place node_modules in another folder outside of the web app?
- Invalid options object. Dev Server has been initialized using an options object that does not match the API schema
- TAR_BAD_ARCHIVE and TAR_ENTRY_INVALID when trying to npm install any package
- Error: Cannot find module 'node:util' while running the nuxt project using npm run command
- React / React-DOM package dependency conflict
- Module not found: Error: Can't resolve 'lodash-es'
- What's the difference between tilde(~) and caret(^) in package.json?
- How to find unused packages in package.json?
- What naming convention do I use for scripts in package.json?
- Pass command line -- argument to child script in Yarn
- Is the "files" property necessary in package.json?
- What's the difference between dependencies, devDependencies, and peerDependencies in NPM package.json file?
- Two vite versions in one NPM package
- How do I resolve peer dependency error: The package react@15.3.2 does not satisfy its siblings' peerDependencies requirements
- Using Environment variable in package.json through dotenv-cli
- Field 'browser' doesn't contain a valid alias configuration
- Troubleshooting 'npm run generate:types' Command Issue
- npx react-native init AwesomeProject error enolocal
- `package.yaml` instead of `package.json` in nodejs
- use npm with different configuration than package.json
- Use git tag or package.json version as Release name in VSTS
- What does "npm:" prefix in dependency section in package.json mean?
- Why (and How Can I FIx) ESLint import/no-extraneous-dependencies Failures on Installed Packages?
- `pnpm install` Usage Error: This project is configured to use yarn
- Multiple Vue.js builds - package workspace problem (Yarn and NPM)
- package.json path don't exist after expo start was run
- NPM CI error bindings not accessible from watchpack-chokidar2:fsevents
- How to deploy a Static website project with bun.lockb to Github Pages?
- Why does my package version resolve to an older version with the caret?
- package-lock.json keeps getting generated automatically despite using pnpm