-
-
Notifications
You must be signed in to change notification settings - Fork 276
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
Use --mode argument to be consistent with Vue CLI #1626
Comments
undergroundwires
added a commit
to undergroundwires/privacy.sexy
that referenced
this issue
Dec 29, 2021
Run quality checks for every possible OS because behavior of linting rules may change per OS (e.g. `linebreak-style` ESLint assertment varies by Unix-like vs Windows). Add a new check to ensure project can be built: 1. As both web and desktop applications. Different jobs are used due to nonidentical environment/mode support. Reference: nklayman/vue-cli-plugin-electron-builder#1627. 2. Targeting all possible modes. The modes are configured using `--mode` but electron CLI checks `NODE_ENV` so it's set as well. Reference: nklayman/vue-cli-plugin-electron-builder#1626. 3. On and for different operating systems. Fix typo "Run units" instead of "Run unit tests". Link to specific GitHub actions page for workflow runs. Update documentation to match new structure, and change nontransparent icons from the diagram and consistently use imperative for actions. Rename `release-site` , `release-git`, `release-desktop` to `site-release` , `git-release` and `desktop-release` to not be Yoda.
undergroundwires
added a commit
to undergroundwires/privacy.sexy
that referenced
this issue
Dec 29, 2021
Run quality checks for every possible OS because behavior of linting rules may change per OS (e.g. `linebreak-style` ESLint assertment varies by Unix-like vs Windows). Add a new check to ensure project can be built: 1. As both web and desktop applications. Different jobs are used due to nonidentical environment/mode support. Reference: nklayman/vue-cli-plugin-electron-builder#1627. 2. Targeting all possible modes. The modes are configured using `--mode` but electron CLI checks `NODE_ENV` so it's set as well. Reference: nklayman/vue-cli-plugin-electron-builder#1626. 3. On and for different operating systems. Fix typo "Run units" instead of "Run unit tests". Link to specific GitHub actions page for workflow runs. Update documentation to match new structure, and change nontransparent icons from the diagram and consistently use imperative for actions. Rename `release-site` , `release-git`, `release-desktop` to `site-release` , `git-release` and `desktop-release` to not be Yoda.
undergroundwires
added a commit
to undergroundwires/privacy.sexy
that referenced
this issue
Dec 30, 2021
Run quality checks for every possible OS because behavior of linting rules may change per OS (e.g. `linebreak-style` ESLint assertment varies by Unix-like vs Windows). Add a new check to ensure project can be built: 1. As both web and desktop applications. Different jobs are used due to nonidentical environment/mode support. Reference: nklayman/vue-cli-plugin-electron-builder#1627. 2. Targeting all possible modes. The modes are configured using `--mode` but electron CLI checks `NODE_ENV` so it's set as well. Reference: nklayman/vue-cli-plugin-electron-builder#1626. 3. On and for different operating systems. Fix typo "Run units" instead of "Run unit tests". Link to specific GitHub actions page for workflow runs. Update documentation to match new structure, and change nontransparent icons from the diagram and consistently use imperative for actions. Rename `release-site` , `release-git`, `release-desktop` to `site-release` , `git-release` and `desktop-release` to not be Yoda.
I'm not sure what you mean by "we do the opposite here," can you elaborate a bit more? |
I'm sorry for my bad formulation. Vue CLI uses
A code snippet example I found is here. So as a workaround, I set both: mode='production'
npm install --global cross-env
cross-env-shell NODE_ENV="$mode"
npm run electron:build -- --publish never --mode "$mode" But it would be nice to be able to skip setting |
LarrMarburger
pushed a commit
to LarrMarburger/privacy.sexy
that referenced
this issue
Nov 16, 2023
Run quality checks for every possible OS because behavior of linting rules may change per OS (e.g. `linebreak-style` ESLint assertment varies by Unix-like vs Windows). Add a new check to ensure project can be built: 1. As both web and desktop applications. Different jobs are used due to nonidentical environment/mode support. Reference: nklayman/vue-cli-plugin-electron-builder#1627. 2. Targeting all possible modes. The modes are configured using `--mode` but electron CLI checks `NODE_ENV` so it's set as well. Reference: nklayman/vue-cli-plugin-electron-builder#1626. 3. On and for different operating systems. Fix typo "Run units" instead of "Run unit tests". Link to specific GitHub actions page for workflow runs. Update documentation to match new structure, and change nontransparent icons from the diagram and consistently use imperative for actions. Rename `release-site` , `release-git`, `release-desktop` to `site-release` , `git-release` and `desktop-release` to not be Yoda.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Vue CLI uses
--mode
argument to setNODE_ENV
however we do the opposite here.It would be nice to be part of Vue convention, this way users can except similar behavior to
npm run electron:build
just likenpm run build
and set the environment in a unified consistent way.It would also simplify understanding of how
vue-cli-service build
is called internally.Unidentical APIs also cause a bug/limitation like #1627
The text was updated successfully, but these errors were encountered: