Replies: 2 comments
-
Nx be whack as hell sometimes. What I did was rename it jest.config.ts.bak instead of deleting. Whatever it's doing checking this file can be bypassed by deleting or renaming. Who needs tests |
Beta Was this translation helpful? Give feedback.
-
Hi @igortas We're aware of some stability issues around Nx plugins. Can you try setting Also checkout the latest Nx 19 release, which has other stability fixes. If you have further issues, I would recommend opening an issue and a repro so we can investigate further. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I'm trying to learn nx and keep it clean as possible, without adding new mess from the current one is generated by
nx
plugins.I'm trying to create dead simple fullstack app, but everytime, I stop writing some code, turn off my pc and return back to the project, trying to continue like normal, sane person, run the same command for the apps in parallel,
nx
behave, like I've uninstalledwindows 11
and switched tolinux
.Any tips, how
nx
can stay not broken, for at least half hour?For example, I've return back to the nx demo app, and for some reason
jest
throws weird error, that never happend. Funny is, I need to run only the apps, not tests, the error is:Yesterday, I was facing cache issues forcing me to manually remove the
.nx
cache, so I can start the project.Installing or upgrading the packages, nx gets frozen with only red error:
NX lock files changed
, once again remove the ```.nx```` cache manually.Two days before, I've replaced
vite.config.ts
file tovite.config.mts
andnx
keeps pointing to.mts.[hash].mjs
file, once again, removing manually the cache.``run-many``` not working sequentially, prevents from runing the next app(s), after initial one (in my case nodejs api)
I can continue going on, out of nowhere blockers.
If anyone has suggestions more how to proceed using nx, without this issues, I like to hear.
BR,
Beta Was this translation helpful? Give feedback.
All reactions