As discussed in #48, I encountered problems using custom namedInputs within the Nx plugin to detect when package targets should be triggered. Which forced me to fall back on default named input (an evil choice I know...)
What would you expect to happen?
No response
What steps did you take?
It turns out this is an Nx issue. See this discussion in Discord for reference.
I can confirm after creating another plugin on Nx 20 here.
After upgrading to Nx 20, use your own namedInput!
BioPhoton
commented
5 days ago
What happened?
As discussed in #48, I encountered problems using custom namedInputs within the Nx plugin to detect when package targets should be triggered. Which forced me to fall back on
defaultnamed input (an evil choice I know...)What would you expect to happen?
No response
What steps did you take?
It turns out this is an Nx issue. See this discussion in Discord for reference. I can confirm after creating another plugin on Nx 20 here.
After upgrading to Nx 20, use your own namedInput!
Code PushUp package version
No response
What operation system are you on?
MacOS
Node version
No response
Relevant log output
No response