We are using nx for our angular library. Since we occasionally have breaking changes where we rename things I would like to provide an automated migration for these changes to run with nx migrate. I searched the docs and tried the generate scripts but did not find a definitive answer on how to build these migrations. I would like to avoid building a second library (besides our existing one) which the consumers need to install just to get the migrations. Best case would be if I could incorporate the migration script into the existing library but it looks like I have to create a plugin, create the migration there and publish it as a separate artifact. Does anyone have a clue if it is possible to add a migration to an existing library? Continue reading...
