-
Notifications
You must be signed in to change notification settings - Fork 9
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
fix(package): fix brittle tests #34
Conversation
package.json
Outdated
@@ -8,7 +8,7 @@ | |||
"test:lint": "eslint ./ --ignore-path .gitignore --ext .js", | |||
"test:lockfile": "lockfile-lint -p package-lock.json -t npm -a npm -o https: -c -i", | |||
"test:git-history": "commitlint --from origin/main --to HEAD", | |||
"test:unit": "jest", | |||
"test:unit": "NODE_ENV=production jest", |
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.
do you know which was the brittle test ? ideally any test that relies on NODE_ENV being set to production should have it set so within the test
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.
Likely the last PR that went in, not sure why the build passed on the PR though
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.
yeah the last PR that went in, it didn't fail because we set the node_env properties on github workflows for tests but that is not the case for the release workflows
🎉 This PR is included in version 3.5.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Fix failing tests on the release process due to missing NODE_ENV value
Description
Motivation and Context
How Has This Been Tested?
Types of Changes
Checklist:
What is the Impact to Developers Using babel-preset-amex?