InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now. Learn more →
Top 7 TypeScript W3c Projects
-
graphql-yoga
🧘 Rewrite of a fully-featured GraphQL Server with focus on easy setup, performance & great developer experience. The core of Yoga implements WHATWG Fetch API and can run/deploy on any JS environment.
Project mention: Show HN: Dumbo – Hono inspired framework for PHP | news.ycombinator.com | 2024-11-17You're talking about the implementation of the protocol, right?
That is a good implementation of it, called GraphQL Yoga[0]
However I'm concerned there is a slight disconnect here. I'm saying that the technical specification of GraphQL does not lend itself to being bad, rather its the failure of developers to really understand its purpose and what its for (its a giant aggregator, with various ways to optimally aggregate things together, depending on what is optimal for a given problem set)
For that, I recommend becoming more familiar with the specification itself[1] because thats what I'm talking about. The specification (and thus its technical nature) doesn't prescribe anything regarding how you get data on to the graph. Many people equate GraphQL with database problems[2]
This doesn't mean I don't understand that GraphQL has shortcomings, but all approaches to APIs have short comings. I have found GraphQL has the least amount
[0]: https://github.com/dotansimha/graphql-yoga
[1]: https://spec.graphql.org
[2]: Common complaint I see all the time. I find it stems from a failure to understand how the entirety of GraphQL is meant to work, and some of the mechanics within. Like when to appropriately leverage DataLoader[3], for instance.
[3]: https://github.com/graphql/dataloader
-
SurveyJS
JavaScript Form Builder with No-Code UI & Built-In JSON Schema Editor. Keep full control over the data you collect and tailor the form builder’s entire look and feel to your users’ needs. SurveyJS works with React, Angular, Vue 3, and is compatible with any backend or auth system. Learn more.
-
papanasi
🥯Papanasi is the Frontend UI library to use cross Frameworks. A set of components to use in Angular, Preact, Qwik, React, Solid, Svelte, Vue and Web Components
-
rdf-validate-shacl
Validate RDF data purely in JavaScript. An implementation of the W3C SHACL specification on top of the RDFJS stack.
-
-
-
contact-picker-api-demo
An API to give one-off access to a user’s contact information with full control over the shared data.
-
-
InfluxDB
InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
TypeScript W3c discussion
TypeScript W3c related posts
-
Create Cookies in GraphQL-Yoga Resolvers using AWS Lambda Integration
-
Announcing GraphQL Yoga v3
-
Apollo server subscriptions in production
-
What Makes Defending GraphQL APIs Challenging to Security Engineers
-
GraphQl subscriptions Nodejs
-
What is Context Propagation in Distributed Tracing?
-
The Anatomy of a GraphQL Request
-
A note from our sponsor - InfluxDB
www.influxdata.com | 9 Jul 2025
Index
What are some of the best open-source W3c projects in TypeScript? This list will help you:
# | Project | Stars |
---|---|---|
1 | graphql-yoga | 8,398 |
2 | papanasi | 598 |
3 | rdf-validate-shacl | 110 |
4 | w3c-keys | 55 |
5 | swarmstr.com | 14 |
6 | contact-picker-api-demo | 6 |
7 | standard-html | 4 |