-
Notifications
You must be signed in to change notification settings - Fork 52
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
nx.json and workspace.json are out of sync #237
Comments
I saw the same issue as Chau and figured I'd create a Dockerfile that illustrates it (also to make sure it's nothing machine related) If you save this content in a file cakked FROM node:14-alpine
WORKDIR /workspace
RUN npm install -g @nrwl/cli create-nx-workspace nativescript
RUN npx create-nx-workspace ns-test --preset empty --no-nx-cloud
WORKDIR /workspace/ns-test
RUN npm install -D @nstudio/xplat
RUN nx generate @nstudio/xplat:application native --platforms nativescript --routing
RUN nx ios nativescript-native
|
This is fixed in
Also, if you're curious with Electron you can generate electron app by targeting any web app in workspace, for example:
Choose 'web' to create a standard web app in workspace. Now you can target it for electron:
Choose 'electron' to create it, then run You'll see the run command print out at top of generation but you can start it given example above with:
|
i will recommend to change following from from ng with nx "build.electron.desktop": "yarn run prepare.electron.desktop && nx build electron-desktop --prod --base-href ./", i was getting error The build command requires to be run in an Angular project, but a project definition could not be found. and also need to add -c.electronVersion=11.1.0 -c.asar=true "build.electron.desktop.windows": "yarn run build.electron.desktop && cd dist/apps/electron-desktop && npx electron-builder build -c.electronVersion=11.1.0 -c.asar=true --windows", without this change was getting below error |
A race condition can cause this to occur when calling externalSchematic in a chain with schematics.
If you encounter this you might share the commands you ran which led to it as we are investigating the condition.
The text was updated successfully, but these errors were encountered: