-
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
[EngSys] Move from ts-node to tsx for tests #28801
Conversation
API change check API changes are not detected in this pull request. |
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.
Thanks for this! Will definitely use this on identity as well. I left a few comments but holding off on approving so we can get more eyes (since auto-merge is enabled) from the team 🚀
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.
🚀
### Packages impacted by this PR @azure/identity ### Describe the problem that is addressed by this PR Follows #28801 to use tsx for running identity tests, which avoids requiring the mocha workarounds ### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen? Using esm4mocha, but I think this is a good path forward to try
### Packages impacted by this PR - @azure/dev-tool ### Issues associated with this PR ### Describe the problem that is addressed by this PR Reverts back to the original for the testing ts-node for JS and TS. ### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen? ### Are there test cases added in this PR? _(If not, why?)_ ### Provide a list of related PRs _(if any)_ - #28801 ### Command used to generate this PR:**_(Applicable only to SDK release request PRs)_ ### Checklists - [x] Added impacted package name to the issue description - [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_ - [ ] Added a changelog (if necessary)
Builds off of Matt's work on moving to tsx in #28801 by removing the `use-esm-workaround` flag from packages that needed it before we moved to tsx. There's additional cleanup to be had, but I am trying not to cause a build storm. We are at a point where we can delete `esm` globally! Contributes to #28617 which can be completed with a no-ci change to remove `esm` globally ****NO_CI****
Packages impacted by this PR
Issues associated with this PR
Describe the problem that is addressed by this PR
Removes dependency on
ts-node
andesm
and moves in favor of usingtsx
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists