-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[mgmt] migrate mgmt package to esm 9 #32366
Conversation
API change check API changes are not detected in this pull request. |
"esm", | ||
"commonjs" | ||
], | ||
"esmDialects": [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we shipping for React-Native and Browser support? If not, please remove the esmDialects
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mpodwysocki do you see any potential risk of adding this support? When we deprecated the very older version of Node SDK, we have this deprecation message "This package is deprecated in favor of @azure/arm-compute whick works both on node.js and browsers" See link which are actually from Ramya at that time, but we do have been ignoring the browser test for mgmt plane https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/databox/arm-databox/package.json#L80 so I was not sure if we want this or not
Perhaps @xirzec has some thoughts here ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After some offline discussion with @mpodwysocki, we are fine with keeping this. Going to merge this for now. @xirzec feel free to let me know if you have any concerns, we can always revisit this :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@qiaozha @mpodwysocki since we shipped browser supported code in dist, should we enable the browser testing also?
Currently we skipped broswer testing by default, not sure any reason not doing that?
azure-sdk-for-js/sdk/databox/arm-databox/package.json
Lines 70 to 76 in 0bcbed4
"integration-test:browser": "echo skipped", | |
"integration-test:node": "dev-tool run test:vitest --esm", | |
"lint": "echo skipped", | |
"minify": "dev-tool run vendored uglifyjs -c -m --comments --source-map \"content='./dist/index.js.map'\" -o ./dist/index.min.js ./dist/index.js", | |
"pack": "npm pack 2>&1", | |
"prepack": "npm run build", | |
"test": "npm run integration-test", |
#32184
@azure/arm-databox
@azure/arm-databoxedge
@azure/arm-databoxedge-profile-2020-09-01-hybrid
@azure/arm-databricks
@azure/arm-datacatalog