You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nx dev team have a pretty rapid release cadence, and they seem fairly ok with changing API's in minor release updates.
I originally wrote this plugin to serve my own requirements which at the time were nx v12.x
What I'm wondering now, is how best to provide plugin support against lots of different nx releases.
Off the top of my head, the simplest approach feels like perhaps there needs to be a plugin release each time there's a new nx release.
At the very least, potentially some sort of CI that can run whenever a new nx release occurs to see if theres a breaking change for the plugin to at least alert us to the need for a new version.
I've no strong opinion on what's best, so ideas are very welcome.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Nx dev team have a pretty rapid release cadence, and they seem fairly ok with changing API's in minor release updates.
I originally wrote this plugin to serve my own requirements which at the time were nx v12.x
What I'm wondering now, is how best to provide plugin support against lots of different nx releases.
Off the top of my head, the simplest approach feels like perhaps there needs to be a plugin release each time there's a new nx release.
At the very least, potentially some sort of CI that can run whenever a new nx release occurs to see if theres a breaking change for the plugin to at least alert us to the need for a new version.
I've no strong opinion on what's best, so ideas are very welcome.
Beta Was this translation helpful? Give feedback.
All reactions