Skip to content

fix: create custom namedInputs inside createNodes #62

Description

@getlarge

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    🐛 bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions