-
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] Use tsx for min/max testing #28890
[EngSys] Use tsx for min/max testing #28890
Conversation
/azp run js - ai-document-intelligence-rest - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
@@ -9,7 +9,7 @@ | |||
"scripts": { | |||
"build": "tsc -p .", | |||
"integration-test:browser": "karma start --single-run", | |||
"integration-test:node": "mocha -r esm-workaround.js -r esm --require source-map-support/register --reporter mocha-multi-reporter.js --reporter-option output=test-results.xml --timeout 350000 --full-trace \"dist-esm/**/{,!(browser)/**/}*.spec.js\" --exit", | |||
"integration-test:node": "mocha --require tsx --require source-map-support/register --reporter mocha-multi-reporter.js --reporter-option output=test-results.xml --timeout 350000 --full-trace \"dist-esm/**/{,!(browser)/**/}*.spec.js\" --exit", |
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.
Should esm-workaround.js be removed as part of this update?
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.
Good Q, it's used for min/max testing and (as of now) for package integration testing. We're working on removing all of this but it'll be a few steps of work:
- Merge this PR
- Merge remove use-esm-workaround #28826
- Let things bake and ensure nightly builds are happy, min/max is happy, etc
- Remove esm-workaround.js
- Remove
esm
as a dependency from all our packages in a NO_CI commit
I think that would cover it
/check-enforcer evaluate |
Packages impacted by this PR
N/A
Issues associated with this PR
Build failures
Describe the problem that is addressed by this PR
esm
is slowly becoming a larger problem for us and we've been on a mission toremove it. min/max tests fail because esm is unable to handle safe-navigation
operators (?.)
While a separate PR switches tests to use tsx, this PR focuses on min/max tests
and can be merged separately.
Provide a list of related PRs (if any)
#28826