We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
ES2023 is 100% supported in Node.js 20 on node.green
docs: update FAQ.md (#341)
Fix: typo in FAQ.md file (#340)
Updated Performance (markdown)
Tweak pprof wording for santization
Document profiling with pprof-it & pprof. (#338) * Document profiling with pprof-it & pprof. * Point out `PPROF_SANITIZE`. * More warning blocks.
Add `moduleResolution` `bundler` to FAQ answer (#337)
Updated Release Activities (markdown)
fix: usage of `node12 which is deprecated` (#335)
Update the TypeScript Real-world plugins list (#326) The `styled-components` plugin was moved. TSLint is deprecated. Astro, MDX, Vue, and Svelte now provide TypeScript plugins.
Fix typo: `complier` -> `compiler` (#322)
fixed typo in "Pre-Declined Feature Requests" title (#333)
Update Breaking-Changes.md (#332) docs: fixing broken URL link in section 3.9
docs: added Bsky and Mastodon (Fosstodon) account mentions (#321)
Recover missing FAQ section on functions/signatures with fewer parameters being assignable to those with more parameters.
Update Node 18 to reflect that it supports lib=ES2023
Update bot commands
Add isFinite
Updated FAQ (markdown)
Merge pull request #325 from jdevries3133/ts_server_perf_details Callout performance characteristics of ts-server
feat: add details re diagnostics
chore: format one sentence per line
Callout performance characteristics of ts-server While reading the guide with an eye for improving the editor experience, I was not sure how ts-server behaves, or how fixing hotspots I view during tracing would change the editing experience. I ended up jumping into Discord for clarity, and this is a summary of what I learned.
Updated All The Bots (markdown)
Remove mention of --trace-ic in favor of dexnode
Change `module` to `node16` where appropriate
Updated No New Utility Types (markdown)
Created No New Utility Types (markdown)