Whatwg

Open-source projects categorized as Whatwg

Top 23 Whatwg Open-Source Projects

  • node-fetch

    A light-weight module that brings the Fetch API to Node.js

  • Project mention: Mastering The Heap: How to Capture and Store Images from Fetch Responses | dev.to | 2024-05-02

    node-fetch.

  • 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.

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • WHATWG HTML Standard

    HTML Standard

  • Project mention: Here are the 10 projects I am contributing to over the next 6 months. Share yours | dev.to | 2024-04-13

    WHAT-WG HTML

  • wpt

    Test suites for Web platform specs β€” including WHATWG, W3C, and others

  • Project mention: Show HN: Dropflow, a CSS layout engine for node or <canvas> | news.ycombinator.com | 2024-03-21

    To reply mostly with my WPT Core Team hat off, mostly summarising the history of how we've ended up here:

    A build script used by significant swaths of the test suite is almost certainly out; it turns out people like being able to edit the tests they're actually running. (We _do_ have some build scripts β€” but they're mostly just mechanically generating lots of similar tests.

    A lot of the goal of WPT (and the HTML Test Suite, which it effectively grew out of) has been to have a test suite that browsers are actually running in CI: historically, most standards test suites haven't been particularly amenable to automation (often a lot of, or exclusively, manual tests, little concern for flakiness, etc.), and with a lot of policy choices that effectively made browser vendors choose to write tests for themselves and not add new tests to the shared test suite: if you make it notably harder to write tests for the shared test suite, most engineers at a given vendor are simply going to not bother.

    As such, there's a lot of hesitancy towards anything that regresses the developer experience for browser engineers (and realistically, browser engineers, by virtue of sheer number, are the ones who are writing the most tests for web technologies).

    That said, there are probably ways we could make things better: a decent number of tests for things like Grid use check-layout-th.js (e.g., https://github.com/web-platform-tests/wpt/blob/f763dd7d7b7ed...).

    One could definitely imagine a world in which these are a test type of their own, and the test logic (in check-layout-th.js) can be rewritten in a custom test harness to do the same comparisons in an implementation without any JS support.

    The other challenge for things like Taffy only targeting flexbox and grid is we're unlikely to add any easy way to distinguish tests which are testing interactions with other layout features (`position: absolute` comes to mind!).

    My suggestion would probably be to start with an issue at https://github.com/web-platform-tests/rfcs/issues, describing the rough constraints, and potentially with one or two possible solutions.

  • parse5

    HTML parsing/serialization toolset for Node.js. WHATWG HTML Living Standard (aka HTML5)-compliant.

  • happy-dom

    A JavaScript implementation of a web browser without its graphical user interface

  • Project mention: Vitest In-Source Testing for SFC in Vue? | dev.to | 2024-04-16

    Next we’ll install Vitest and happy-dom to the project by running:

  • fetch

    Fetch Standard (by whatwg)

  • Project mention: JavaScript fetch does not support GET request with body | news.ycombinator.com | 2023-11-21
  • SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

    SaaSHub logo
  • validator

    Nu Html Checker – Helps you catch problems in your HTML/CSS/SVG (by validator)

  • dom

    DOM Standard

  • Project mention: HTML Attributes vs. DOM Properties | news.ycombinator.com | 2024-04-24

    What I said in my previous comment is observably true. Try making a demo where it isn't.

    > A DOM node is a living mutable thing, but the JavaScript object representing that node is not.

    The JavaScript object is mutable. The first example in the article shows this.

    > That is also why a node list is not an array.

    Modern APIs on the web return platform arrays (eg JavaScript arrays). https://webidl.spec.whatwg.org/#js-sequence - here's where the WebIDL spec specifies how to convert a sequence to a JavaScript array.

    I'm fully aware of NodeList. There's a reason the spec calls them "old-style" https://dom.spec.whatwg.org/#old-style-collections

    > I can understand how this is confusing if you have never operated without a framework, but otherwise it’s really straightforward

    Sighhhhhh. I've been a web developer for over 20 years, and spent a decade on the Chrome team working on web platform features. Most of my career has been on the low-level parts of the platform.

    Could it be possible that people are disagreeing with you, not because they're stupid, but because you're in the wrong? Please try to be open minded. Try creating some demos that test your opinions.

  • streams

    Streams Standard

  • Project mention: Backpressure explained – the resisted flow of data through software | news.ycombinator.com | 2024-03-27

    Yup, this is what WHATWG's Streams spec[0] (linked in the article) says. It defines backpressure as a "process of normalizing flow from the original source according to how fast the chain can process chunks" where the reader "propagates a signal backwards through the pipe chain".

    Mozilla's documentation[1] similarly defines backpressure as "the process by which a single stream or a pipe chain regulates the speed of reading/writing".

    The article confuses backpressure (the signal used for regulation of the flow) with the reason backpressure is needed (producers and consumers working at different speeds). It should be fairly clear from the metaphor, I would have thought: With a pipe of unbounded size there is no pressure. The pressure builds up when consumer is slower than producer, which in turn slows down the producer. (Or the pipe explodes, or springs a leak and has to drop data on the ground.)

    [0] https://streams.spec.whatwg.org/#pipe-chains

    [1] https://developer.mozilla.org/en-US/docs/Web/API/Streams_API...

  • observable

    Observable API proposal

  • Project mention: Proposal: Signals as a Built-In Primitive of JavaScript | news.ycombinator.com | 2024-03-31
  • url

    URL Standard

  • Project mention: Cool URIs can be ugly | news.ycombinator.com | 2024-02-14

    Semicolon (;) has no special meaning in a URL. You can ascribe it a meaning in your particular routing, but the spec has nothing to say about it.

    https://url.spec.whatwg.org/

  • swift-url

    A new URL type for Swift

  • encoding

    Encoding Standard (by whatwg)

  • Project mention: Transcoding Latin 1 strings to UTF-8 strings at 12 GB/s using AVX-512 | news.ycombinator.com | 2023-08-21

    Be aware that with the WHATWG Encoding specification [1], that says that latin1, ISO-8859-1, etc. are aliases of the windows-1252 encoding, not the proper latin1 encoding. As a result, browsers and operating systems will display those files differently! It also aliases the ASCII encoding to windows-1252.

    [1] https://encoding.spec.whatwg.org/#names-and-labels

  • console

    Console Standard (by whatwg)

  • Project mention: Why can you overrule console.log? | /r/learnjavascript | 2023-12-09

    console is not part of the JavaScript programming language. WHATWG has published Console Standard https://console.spec.whatwg.org/ though console is not defined in ECMA-262.

  • HTMLKit

    An Objective-C framework for your everyday HTML needs.

  • standards-positions

    WebKit's positions on emerging web specifications (by WebKit)

  • Project mention: iOS404 | news.ycombinator.com | 2024-04-16

    You can check why Mozilla and Apple have opted to not support this.

    https://github.com/mozilla/standards-positions/issues/154

    https://github.com/WebKit/standards-positions/issues/28

    Neither Mozilla or Webkit are satisfied that the proposal is safe by default, and contains footguns for the user that can be pretty destructive.

  • fs

    File System Standard (by whatwg)

  • Project mention: persistent storage API on Firefox temporary extension | /r/learnjavascript | 2023-07-24

    You can use File System Standard https://fs.spec.whatwg.org/ to write data for that origin (Firefox doesn't implement File System Access API, nonetheless a File object can still be written to local disk using File API).

  • html5gum

    A WHATWG-compliant HTML5 tokenizer and tag soup parser

  • notifications

    Notifications API Standard

  • meta

    Discussions and issues without a logical home (by whatwg)

  • sg

    A place to raise issues with the WHATWG Steering Group (by whatwg)

  • SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

    SaaSHub logo
NOTE: The open source projects on this list are ordered by number of github stars. The number of mentions indicates repo mentiontions in the last 12 Months or since we started tracking (Dec 2020).

Whatwg related posts

Index

What are some of the best open-source Whatwg projects? This list will help you:

Project Stars
1 node-fetch 8,646
2 graphql-yoga 8,029
3 WHATWG HTML Standard 7,710
4 wpt 4,632
5 parse5 3,554
6 happy-dom 2,925
7 fetch 2,078
8 broken-link-checker 1,872
9 validator 1,635
10 dom 1,535
11 streams 1,331
12 observable 516
13 url 507
14 swift-url 330
15 encoding 266
16 console 265
17 HTMLKit 236
18 standards-positions 232
19 fs 208
20 html5gum 146
21 notifications 131
22 meta 94
23 sg 63

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com