TypeScript-wiki
proposal-pattern-matching
TypeScript-wiki | proposal-pattern-matching | |
---|---|---|
6 | 67 | |
668 | 5,344 | |
0.6% | 0.9% | |
6.7 | 9.0 | |
10 days ago | 12 days ago | |
JavaScript | HTML | |
Creative Commons Attribution 4.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
TypeScript-wiki
-
Typescript Runtime Validators and DX, a type-checking performance analysis of zod/superstruct/yup/typebox
What's prompted me to look at this is my tRPC+Zod editor experience at work has become unusable. 2-3 seconds to just get autocompletion options on a tRPC path, and then another 2-3 for the next path, repeat. When investigated using TypeScript's tracing tools the data entirely points back to my team's Zod DTOs. What I learned is that Zod's performance is okay at the start, but when you start using methods like .extend/.pick/.omit (and so on) the performance regresses in the order of a magnitude. Rather than making this into a "Zod considered bad" post, I wanted to investigate how the alternatives which can be integrated with tRPC fare, and see whether I can do better.
- 10-25% faster typescript compile times, 43% smaller npm package after Typescript codebase converted to modules
- How to find the type that is causing performance issues in VsCode?
-
Ten Years of TypeScript
When you can write a busy beaver machine in the type system, LOC ceases to be a good indicator or how long something should take to typecheck, imo. If you're frustrated with your build, you should use the trace tools on the TS wiki[1] to track down what types are slow to check, so you can attribute the slowness to the appropriate library authors/yourself and decide for yourself if the speed/correctness tradeoff they've made is right for you.
[1]https://github.com/microsoft/TypeScript-wiki/blob/main/Perfo...
-
Typescript type checking performance in big codebases?
Good spot to start: https://github.com/microsoft/TypeScript-wiki/blob/main/Performance-Tracing.md
-
How to upgrade TypeScript versions - what's your process regarding breaking changes?
So I want to update my (very large*) project from TypeScript 2.3.3 to the latest version, and I know that a breaking changes doc exists.
proposal-pattern-matching
-
Coming to grips with JS: a Rubyist's deep dive
Note, however, that there is a proposal to add pattern matching to JS.
-
Level up your Typescript game, functionally - Part 2
There's an ECMAScript proposal that is in the works to add this feature to the language! It's going to look something like this.
-
Building React Components Using Unions in TypeScript
More importantly, TypeScript typically commits to build things into itself when the proposal in JavaScript reaches Stage 3. The pattern matching proposal in JavaScript is Stage 1, but depends on many other proposals as well that may or may not need to be at Stage 3 as well for it to work. This particular proposal is interested on pattern matching on JavaScript Objects and other primitives, just like Python does with it’s native primitives. These are also dynamic types which helps in some areas, but makes it harder than others. Additionally, the JavaScript type annotations proposal needs to possibly account for this. So it’s going to be awhile. Like many years.
-
Explicit Software Design. Preliminary Conclusions
For true™ functional programming in JS, native pattern matching and partial function application are missing (at least for now: 1, 2). For proper OOP, it lacks real interfaces and compile-time dependency injection.
-
TypeScript Is Surprisingly OK for Compilers
The proposal for pattern matching syntax seems more akin to what they're looking for.
https://github.com/tc39/proposal-pattern-matching
-
[AskJS] C# in every Node.js job posting?
There's a proposal to add something like that to JavaScript but it's been stuck in limbo since 2017 although there are libraries like ts-pattern which implement it already.
-
[AskTS] What do you think will be the future of runtime type checking?
I'll admit, it is easy to assert that the TypeScript language should not be involved in the matters of packages but I also wonder if we're moving towards a point where interfaces will be as common as namespaces and whether or not it would be sensible for the language to incorporate such type assertions into the language formally, after all, it already compiles to various forms of JavaScript and there is a stage 1 proposal submitted to the TC39 committee to give JavaScript pattern matching. If adopted, wouldn't it make sense to allow TypeScript to compile a type into a type guard for the native JavaScript pattern matcher?
- Updates from the 96th TC39 meeting
-
Mostly adequate guide to FP (in JavaScript)
Both are active tc39 proposals :)
https://github.com/tc39/proposal-pipeline-operator - Stage 2
https://github.com/tc39/proposal-pattern-matching - Stage 1
Hopefully we get both in the next couple of years.
-
CoffeeScript for TypeScript
We often add promising TC39 proposals into Civet so people can experiment without waiting.
We've added https://github.com/tc39/proposal-pipeline-operator, a variant of https://github.com/tc39/proposal-pattern-matching, a variant of https://github.com/tc39/proposal-string-dedent and others.
Since our goal is to be 99% compatible with ES we'll need to accommodate any proposals that become standard and pick up anything TC39 leaves on the table (rest parameters in any position, etc.)
What are some alternatives?
hacl-star - HACL*, a formally verified cryptographic library written in F*
fp-ts - Functional programming in TypeScript
gapstack - The missing utilities and tools for React and the Javascript/Typescript ecosystem
package.elm-lang.org - website for browsing packages and exploring documentation
content - The content behind MDN Web Docs
ecma262 - Status, process, and documents for ECMA-262
proposal-pipeline-operator - A proposal for adding a useful pipe operator to JavaScript.
proposal-record-tuple - ECMAScript proposal for the Record and Tuple value types. | Stage 2: it will change!
ts-pattern - 🎨 The exhaustive Pattern Matching library for TypeScript, with smart type inference.
xstate - Actor-based state management & orchestration for complex app logic.
await-to-js - Async await wrapper for easy error handling without try-catch
proposal-import-assertions - Proposal for syntax to import ES modules with assertions [Moved to: https://github.com/tc39/proposal-import-attributes]