Conversation
|
|
✅ Deploy Preview for trusting-lumiere-9c7fad ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Pull request overview
Updates Remeda’s TypeScript configuration to explicitly include Node.js ambient type definitions, aligning with TypeScript’s move toward requiring explicit types opt-ins (as surfaced by the canary job failure).
Changes:
- Add
"types": ["node"]topackages/remeda/tsconfig.jsonto ensure Node globals/modules are typed during compilation and in editor tooling.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1282 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 174 174
Lines 1622 1622
Branches 392 392
=========================================
Hits 1622 1622 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
commit: |
|
🎉 This PR is included in version 2.33.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Blame: microsoft/TypeScript#63054
TypeScript are moving to explicit types instead of catch-all by default. This means that projects need to have a types entry if they want to rely on additional types.
This was surfaced by our canary job on February 5: https://github.com/remeda/remeda/actions/runs/21703126297/job/62587774821