Last 12 weeks · 0 commits
3 of 6 standards met
Updates 0.96.2 → 0.109.0 along with the rest of the deno ecosystem crates (, , , , , , , , , ) to their latest mutually-compatible versions. The new crates use let-chains, so the rust toolchain is bumped 1.86.0 → 1.88.0. Also updates 0.27 → 0.29 (which bundles TypeScript 6.0): adds , since TS 6.0 turns and into deprecation errors that abort the type check TS 6.0 no longer auto-discovers the packages installed in the output's , so they're now enumerated and included explicitly via the compiler option Removes the obsolete shim. Deno now returns the same type from / as node, so coercing them back to is no longer necessary. Notes The deprecated options silenced by (notably ) will become hard errors in TS 7.0 — worth migrating in a future change. Tested locally: (rust) and (type-check on) both pass.
Temporal has moved to stage 4. As such, I would like to start building libs assuming is available, delegating the responsibility to polyfill if needed to the user. However, I don't see how to configure dnt in order to make the TS compiler aware of the namespace: Could you help me with that ? Cheers 🍻
Repository: denoland/dnt. Description: Deno to npm package build tool. Stars: 1325, Forks: 49. Primary language: Rust. Languages: Rust (55.4%), TypeScript (44.5%), JavaScript (0.1%). License: MIT. Latest release: 0.42.3 (11mo ago). Open PRs: 9, open issues: 105. Last activity: 11mo ago. Community health: 50%. Top contributors: dsherret, Gaubee, g-plane, UrielCh, kt3k, hyp3rflow, rojvv, char, ah-yu, utajum and others.