-
Notifications
You must be signed in to change notification settings - Fork 19
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
Multiple plugin issues #23
Comments
Well that's not right. We use this plugin for the main nx repo, so it should be working. What's the version of your nx workspace? Or is there some kind of reproduction I can see? |
I have the latest nx installed v16.4 (for both the cli for the new nx monorepo and in the monorepo I tried to add to) MacOSX m1, node v18.12 |
I just realised the fresh version was on v14 by default on the generator. If I run this I and upgrade the default generator project to nx v16 then none of the builds work at all
Then if I run
|
I couldn't see your original issue, but I did notice some things with the dependencies not matching. Can you give it a shot again with |
No same issue unfortunately (for both scenarios - mixed existing repo saying daemon was terminated and new repo with just rust saying "Failed to process the project graph with "nx-js-graph-plugin"). Here is the repro of the 2nd scenario (clean rust only, upgraded to latest nx and using your latest 1.2.0) - https://github.com/jcbdev/monodon-plugin-issue-repro If you need anything else let me know. |
Actually. I just killed the node_modules/yarn.lock after upgrading the library to 1.2.0 as you suggested and reinstalled all of the packages from scratch and the rust only clean repo works 🤔 I tried on the other project (existing & mixed js/rust) and see if it's some dependency issue but it still crashes in the same way with the plugin enabled. |
Yea. The There's an issue with it related with project roots having a ".", and comparing it with a blank "". I'm gonna fix it in the nx repo. |
hey @jcbdev, can you give it a shot again with Nx 16.5.0? |
I had the same problem; pretty hard to track down precisely what is causing it. The behavior on my end is that randomly it simply stopped working between commits. It's probably something related to breaking changes on Nx internals and the version used. Checking daemon.log yields:
Debugging the plugin behavior, I could find that the fileMap is not being generated correctly on the constructor of I will go ahead and create a Pull Request with this fix. |
v1.3.2 should be using the new nx apis, so give it a shot and let me know. Thanks! |
I upgraded and had no issues so far. Everything seems to be working great! 🎉 |
I have been evaluating both this and the @nxrs/cargo plugins and I liked the idea of this because of the integration with napi out of the box.
Unfortunately whereas I can get the other lib to work quite seamlessly I am struggling in multiple ways with this one.
For a start if I try to integrate into an existing repository then I can create a new library, but no nx build/test/lint/graph command will work for ANY project (including the non-rust based ones in the project before the addition).
I have found that if I comment out the following in the nx.json then the builds start to work again but this seems like the wrong thing to do
Otherwise each command fails instantly like so:
Alternatively I tried a completely fresh project like so:
but trying to run project specific commands from the monorepo root fail with the error
you HAVE to change the current directly to the libs/my_rust_node_lib for the command to work which is not how any other NX command normally works.
The text was updated successfully, but these errors were encountered: