Skip to content
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

fix: create custom namedInputs inside createNodes #62

Open
getlarge opened this issue Nov 9, 2024 · 1 comment
Open

fix: create custom namedInputs inside createNodes #62

getlarge opened this issue Nov 9, 2024 · 1 comment
Labels
🐛 bug Something isn't working

Comments

@getlarge
Copy link
Collaborator

getlarge commented Nov 9, 2024

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 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!

Code PushUp package version

No response

What operation system are you on?

MacOS

Node version

No response

Relevant log output

No response

@getlarge getlarge added the 🐛 bug Something isn't working label Nov 9, 2024
@BioPhoton
Copy link
Contributor

related #57

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants