You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The upgrade from tap v11.1.5 to v18.0.0 is a major migration with significant breaking changes, primarily introduced in version 18. This upgrade requires substantial changes to configuration, test code, and CI/CD processes.
Key Breaking Changes:
Complete Overhaul in v18: Version 18 was rewritten in TypeScript and moved to a plugin-based architecture. Features like TypeScript support, mocking, and most assertion methods are now managed as optional plugins that may need to be installed and configured separately.
Coverage System Replaced: The coverage engine was switched from nyc to c8. Consequently, many CLI flags and configuration options related to nyc (e.g., --cov, --no-cov, --check-coverage) have been removed. Coverage is now enabled by default, and not meeting 100% coverage is considered a test failure.
Configuration and CLI Changes: Many configuration options and CLI flags from v16 and earlier are deprecated or have been replaced. For example, tap repl replaces tap --watch, and generating a coverage report is now done with tap report.
API and Behavior Changes:
Callbacks have been removed from t.beforeEach and t.afterEach in favor of promise-based approaches.
The t.test() method's promise now resolves to the child test's results instead of the parent's.
Support for Node.js versions below 10 was dropped in v15.
Recommendation: This is a major refactoring effort that requires careful planning. Developers must review the official v18 upgrade guide, update their configuration files, install necessary plugins for previously built-in functionality, and adapt their test code to the new APIs and coverage behavior.
Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
package.jsonpackage-lock.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-LODASH-15869619
SNYK-JS-HANDLEBARS-15813000
Breaking Change Risk
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Time-of-check Time-of-use (TOCTOU) Race Condition
🦉 Prototype Pollution