Maor Leger

We will be GAing packages in January, so we will not be able to move these over in December; however, we can do the migration on a feature branch or...

Also related https://github.com/Azure/azure-sdk-for-js/issues/21188 which will be unblocked once we move to core v2

We will experiment with supporting compatibility for existing GA'd packages. Starting with KV Admin, which is already migrated over, GA'd, and is currently in beta for the next version, I...

I haven't caught up with the conversations yet but as far as delivering on this experiment I probably don't have the bandwidth to take in all the increased scope here......

Another potential breaking change might be that > FullOperationResponse is not 100% compatible with HttpOperationResponse. For example, the http headers type is different. We may have to re-define. From https://github.com/Azure/azure-sdk-for-js/pull/18736#discussion_r755370326

Any thoughts on which milestone we should move this to?

I was thinking you might be able to do the following: 1. Take the list of dependencies as they're currently defined in `packageFileGenerator` 2. Fetch https://raw.githubusercontent.com/Azure/azure-sdk-for-js/main/sdk/template/template/package.json and parse it 3....

> @maorleger Am I correct in assuming that you want the rollup to be generated as "https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/formrecognizer/ai-form-recognizer/rollup.config.js"? Could you please confirm? Yeah, that's what I was thinking originally - would...

> @maorleger, currently code gen does not add dev-tool to the devDependencies list because the code gen smoke tests build generated packages and dev-tool is not published. The current approach...

Note: this could be related to https://github.com/Azure/azure-sdk-for-js/issues/20690