Skip to content
This repository has been archived by the owner on Oct 7, 2024. It is now read-only.

Angular Ionic: Upgraded to Latest Version and now build runs for every command in project.json #2

Open
JackLazenbyZigzag opened this issue Oct 6, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@JackLazenbyZigzag
Copy link

JackLazenbyZigzag commented Oct 6, 2023

Describe the bug
Not sure if this is a bug or just a setting we're not fully understanding, to be honest!

We recently upgrade our Nx version from 14 to the latest version 16.10.0. As part of this upgrade, we moved from
@nxtend/capacitor:cap
to
@nxext/capacitor:cap

Following this upgrade, any Nx command that we run in order to sync or run our Ionic App will do a build of the app. This would be fine, but it won't let us specify the configuration (such as production) and so it will always build using development settings, unless we use the defaultConfiguration field. Is there a way we can either pass in a flag to determine the configuration being used for these commands (notably sync and open) or can we switch off the build always being performed for these commands? In nxtend, each command didn't run a build beforehand, only the build command did, which is desired behaviour for our needs.

To Reproduce
Attached is an example of our project.json for the sync command that is currently failing for us:

"sync": { "executor": "@nxext/capacitor:cap", "options": { "cmd": "sync", "packageInstall": true, "preserveProjectNodeModules": true }, "configurations": { "ios": { "cmd": "sync ios" }, "android": { "cmd": "sync android" } } },

Expected behavior
Either the ability to specific a configuration so every build performed, regardless of command, uses that configuration, or the ability to turn off builds running for non-build commands.

Additional context
Happened moving from
@nxtend/capacitor:cap
to
@nxext/capacitor:cap

@JackLazenbyZigzag JackLazenbyZigzag added the bug Something isn't working label Oct 6, 2023
@DominikPieper DominikPieper transferred this issue from nxext/nx-extensions Oct 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant