-
Notifications
You must be signed in to change notification settings - Fork 0
Bump knip from 5.61.3 to 5.64.2 in /web-app #22
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
Conversation
Bumps [knip](https://github.com/webpro-nl/knip/tree/HEAD/packages/knip) from 5.61.3 to 5.64.2. - [Release notes](https://github.com/webpro-nl/knip/releases) - [Changelog](https://github.com/webpro-nl/knip/blob/main/packages/knip/.release-it.json) - [Commits](https://github.com/webpro-nl/knip/commits/5.64.2/packages/knip) --- updated-dependencies: - dependency-name: knip dependency-version: 5.64.2 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
✓ Safe to upgradeI recommend merging this upgrade because it includes 21 new features and 41 bug fixes with no breaking changes affecting this project. The reported breaking change about TypeScript v7 incompatibility does not apply since the project uses TypeScript v5.5.3. The renamed re-exports change is an internal knip improvement that enhances how it handles module exports without requiring configuration changes. As a development-only tool for detecting dead code, this upgrade poses no risk to runtime functionality and will benefit from the latest bug fixes and improvements. What we checked
Dependency UsageKnip is a development tool used exclusively for code quality and maintenance in the web application, invoked via the "find-deadcode" npm script to detect unused exports, dependencies, and files across the React-based frontend codebase. The configuration file scopes the analysis to the project's TypeScript/JavaScript source files while strategically excluding the API directory, enabling developers to maintain a clean codebase by identifying and removing dead code. This is a development-time dependency that supports codebase hygiene and technical debt reduction rather than runtime business functionality.
Other Usages (1)These usages were analyzed but no breaking changes were detected: knip
ChangesCRITICAL BREAKING CHANGES: knip is now incompatible with TypeScript version 7, and renamed re-exports are now prioritized which may change how exports are detected. The update includes 41 bug fixes addressing ESLint config errors, Next.js sitemap handling, dynamic import analysis, and binary detection, plus 21 new features including plugins for rstest, bumpp, env-cmd, and GitHub Actions reporting.
View 131 more changes
References (5)[1]: Project uses TypeScript ^5.5.3, making the breaking change about TypeScript v7 incompatibility irrelevant [2]: Knip upgraded from 5.61.3 to 5.64.2 as a devDependency, not affecting production runtime [3]: Configuration uses standard KnipConfig type and syntax compatible with the new version [4]: Knip is used only via 'find-deadcode' script for development-time code quality analysis [5]: Official documentation confirms minimal impact for major version upgrades - users typically don't need code changes (source link) fossabot analyzed this PR using static analysis and dependency research. |
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
|
Superseded by #23. |
Bumps knip from 5.61.3 to 5.64.2.
Release notes
Sourced from knip's releases.
... (truncated)
Commits
f68098dRelease 5.64.2dde7a80fix: Mark nested Next.js sitemaps as entrypoints (#1287)3efb8a3Fix ESLint config error (#1286)b6ac28cfeat: detect vitest ui mode (#1284)e687287Fix config hints4c72030Fix lint issued7e7866Refactor config hints a bit for perf tweak7abdc69Fix config hints in production mode (resolves #1279)dbdd98brefactor: usetoC12configforbumpplugin (#1280)e0ff0b5Release 5.64.1Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)