Conversation
✅ Deploy Preview for detsys-ts-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
📝 WalkthroughWalkthroughThis PR updates seven devDependencies in Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@package.json`:
- Line 45: The package.json upgrade to tsdown v0.20.x introduces a breaking
change: the dts plugin no longer supports the dts.resolve option; inspect
package.json and any tsdown config files for uses of "tsdown" and the
"dts.resolve" option (or references in build scripts invoked by npm run build)
and remove or replace those usages with the new dts plugin configuration format;
update the tsdown config to the v0.20+ plugin API (or lock tsdown to 0.19.x if
you cannot migrate) and then run npm run build to verify the build succeeds,
adjusting any plugin options until the build is green.
| "globals": "^17.0.0", | ||
| "prettier": "^3.8.0", | ||
| "tsdown": "^0.19.0", | ||
| "globals": "^17.1.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
echo "=== Checking tsdown npm registry info ==="
curl -s https://registry.npmjs.org/tsdown | jq -r '.versions["0.20.1"].description, .versions["0.19.0"].description' 2>/dev/null || echo "Could not fetch from npm registry"
echo ""
echo "=== Checking tsdown repository and recent releases ==="
curl -s https://registry.npmjs.org/tsdown | jq -r '.repository.url // .bugs.url // "No repo info"' 2>/dev/nullRepository: DeterminateSystems/detsys-ts
Length of output: 280
🌐 Web query:
tsdown changelog 0.20.1 breaking changes
💡 Result:
tsdown v0.20.1 (Jan 22, 2026) does not list any breaking changes in its release notes; it only includes a feature: inline-only: show warnings if bundled dependencies. [1][2]
If you’re upgrading from v0.20.0 → v0.20.1, the documented breaking change is in v0.20.0, not v0.20.1: upgraded the dts plugin and removed the dts.resolve option. [1]
Sources:
[1] (github.com)
[2] (github.com)
Citations:
🌐 Web query:
tsdown 0.20.1 release notes
💡 Result:
tsdown v0.20.1 (released Jan 22)
- Feature:
inline-only— show warnings if dependencies were bundled. [1]
Sources:
[1] (github.com)
Citations:
Review and address breaking change in tsdown v0.20.0.
The tsdown update from 0.19.0 to 0.20.1 includes a breaking change introduced in v0.20.0: the dts plugin was upgraded and the dts.resolve option was removed. Verify that the build configuration does not rely on the removed dts.resolve option and that npm run build completes successfully.
The globals bump to 17.1.0 is backward compatible.
Also applies to: 47-47
🤖 Prompt for AI Agents
In `@package.json` at line 45, The package.json upgrade to tsdown v0.20.x
introduces a breaking change: the dts plugin no longer supports the dts.resolve
option; inspect package.json and any tsdown config files for uses of "tsdown"
and the "dts.resolve" option (or references in build scripts invoked by npm run
build) and remove or replace those usages with the new dts plugin configuration
format; update the tsdown config to the v0.20+ plugin API (or lock tsdown to
0.19.x if you cannot migrate) and then run npm run build to verify the build
succeeds, adjusting any plugin options until the build is green.
grahamc
had a problem deploying
to
detsys-pr-bot
GitHub Actions
Failure
2 participants
Description
Checklist
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.