-
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
HELP PLEEEEEASE! Bug in in latest version 20.0.3. #329
Comments
@SemAiSoft I have the same issue... if its any help, the last version that I can get to work is with the following commands npx [email protected] workspace I am trying to figure out how to get a more recent release to work... will let you know if I figure it out. |
@SemAiSoft I got nx19 to work by doing this.. npx [email protected] workspace note: after you create your workspace add a .npmrc file to the root of your workspace to deal with legacy stuff.. For the moment I still have not figured out how to get v20 working. |
Thanks so much for the guide. Have tried nx reset. Any other ways to resolve this? |
@SemAiSoft in order for my solution to work you must start fresh, the commands I gave you will not work in an existing repo... that is you MUST start fresh |
Yes, thank you. The point I also have to install all the nx plugins by 'nx add' command, that allows to be properly initiated and configured. |
@SemAiSoft I use this command to first get xplat installed correctly for both web and nativescript That installs cypress and other packages... then I can go on and create apps with this command Currently I am not having a problem with that. I am also running LTS for node... perhaps that is the difference. I also run on a Mac... maybe there is a difference on Windows? |
Thanks so much bro. It just that I like their architectural organizations, else I would have gave up. BIG THANKS for the support |
@SemAiSoft for the moment xplat will not work on Angular 19.. 18 is fine. I am working on a work-around... I have been using xplat for years... I do like how its organized... perhaps @NathanWalker can weigh in on the correct way to make it work? I just finished marking all of the xplat modules to standalone:true... but there are also a few more things with scss |
Well well well, after millions of installs, reinstall, rm node_modules, rm .nx, etc... I finally settle for version 19.0.0 AND only web (nativescript, angular) apps creations. Nest and Electron are not working. I hope this will be fixed soon as this is GREAT LAYER. Thanks to All. |
Angular 19 isn't supported by nx yet. Once it is, nx will automatically migrate all components to standalone: false, I imagine. |
@edusperoni Thanks! I totally forgot to check if NX had caught up to Angular v19... yes, I agree.. it most likely "just work" once NX merges the Angular/v19 branch.. looks like they are close. |
@SemAiSoft @edusperoni Looks like NX will be releasing soon! So I figure we just need to then get a new XPLAT and things will be back to normal for us that want the latest and greatest? |
@edusperoni NX now supports angular 19, would you be able to update xplat? |
@edusperoni @NathanWalker is there any ETA when xplat will be able to install on the latest version a fresh workspace? Currently it's not working and fails where you init with this error. I have tried it with and without installing eslint and fails both for web and nativescript setup... I also ensured that the xplat directory does not exist (as indicated in the error) Any ideas? `npx nx@latest g @nstudio/xplat:init NX Generating @nstudio/xplat:init ✔ Would you like to generate xplat supporting architecture now? You can also generate later with: nx generate @nstudio/xplat:init · web NX Cannot create a new project features at libs/xplat. A project already exists in this directory. |
No way yet! The best is to stick with v19.0.0, not bad since Angular is same version. |
I followed the docs instruction, but can get it together running.
It kept failing during installation, as shown below. Using v19 is not working too.
Even though this is a fresh new project!
The text was updated successfully, but these errors were encountered: