linkedom
wpt
Our great sponsors
linkedom | wpt | |
---|---|---|
10 | 7 | |
823 | 3,865 | |
- | 1.6% | |
8.2 | 9.9 | |
14 days ago | 3 days ago | |
HTML | HTML | |
ISC License | GNU General Public License v3.0 or later |
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.
linkedom
-
The Fetch API is finally coming to Node.js
I recently started using linkedom for this and it has been an absolute joy
- LinkeDOM: A Jsdom Alternative (2021)
-
Happy-DOM: a jsdom alternative that can server side render web components
This looks great. I wonder how it compares to linkedom (repo[1], writeup[2]), which I have found to be fantastic.
[1]: https://github.com/WebReflection/linkedom
[2]: https://webreflection.medium.com/linkedom-a-jsdom-alternativ...
-
Testing Solid.js code beyond jest
linkedom, fastest, but lacks essential features
-
Using Mocha to test ClojureScript
Other things to do would be to use linkedom instead of JSDom, look into a better assertion library than assert etc.
-
Idiosyncrasies of the HTML Parser
Sounds somewhat similar to linkedom[1], which performs nicely.
- LinkeDOM – A triple-linked lists based DOM“ [Live with Andrea Giammarchi]
- LinkeDOM: A Jsdom Alternative
- LinkeDOM - A faster, ESModule friendly, and more readable alternative to JSDOM
wpt
-
Sorry Safari Team
> due to a bug in the testing framework
the "bug" is https://github.com/web-platform-tests/wpt/issues/31147
MacOS 11 isn't allowed(?) to be virtualized, so the Safari TP, which is tied to MacOS updates, couldn't be updated.
> That's why there's uproar
Was there an uproar? There were some objections from some Safari devs that they understood the difficulty in getting the latest number since the web platform test runner can't run the latest Safari Tech Preview (which they've also known for some time), but since the whole point of this was to show how browsers have improved their compatibility on this set of tests, it was hurtful and counterproductive to leave out their latest work. Chrome devs apologized and now we have this article, and it looks like the test runner will start running WebKitGTK for this set of tests so at least the Compat 2021 dashboard[1] will show the latest results.
-
Show HN: Micro HTTP server in 22 lines of C
For clients, browser-compatible HTTP/1 implementation is a whole another bag of problems.
For example, Content-Length isn't just a single header with an integer, like the spec says. You need to support responses with multiple Content-Length headers, and Content-Length with comma-separated list of lengths. Getting this wrong will make your client hang, consume garbage, or allow response stuffing.
https://github.com/web-platform-tests/wpt/pull/10548/files
This problem does not exist in HTTP/2.
-
IndexedDB is completely broken in latest Safari
I assume you're aware of the WPT project (contributed to by all of the major browser vendors these days), and its CSS 2.1 coverage is lacking in a way I'm unaware of.
But for others who don't know:
https://web-platform-tests.org/
https://github.com/web-platform-tests/wpt/tree/master/css/CS...
- Show HN: Webpage Crashes the Chrome Renderer
-
The hotdog web browser and browser engine
https://github.com/danfragoso/thdwb/blob/655eac96e4faa141cb4...
That's not an html parser. It's just some code that regexes strings looking for brackets.
Projects like this are good ways to learn and have fun, but they're many years away from being a browser, even if we limit the scope to the specs of say 2012.
Also fwiw, if you're implementing a browser use the web platform tests instead of writing your own:
-
Deno 1.9 – native http2, performance boost, blob and import completion support
There's the web APIs which are tested against https://github.com/web-platform-tests/wpt (albeit without full coverage), and there is ffi/plugins - for deno specific things like readFile.
I don't know the history of Node... but why would there need to be a diversion?
What are some alternatives?
happy-dom - Happy DOM is a JavaScript implementation of a web browser without its graphical user interface. It includes many web standards from WHATWG DOM and HTML.
HTMLKit - An Objective-C framework for your everyday HTML needs.
firefox-user.js-tool - Interactive view, compare, and more for Firefox user.js (eg arkenfox/user.js) + about:config functions
browsh - A fully-modern text-based browser, rendering to TTY and browsers
ioccc - My IOCCC submissions and practice.
thdwb - 🌭 The hotdog web browser and browser engine 🌭
firefox-ios - Firefox for iOS
element-internals-polyfill - A polyfill for the element internals specification
tuesday-js - simple web-based, free and open-source visual novel editor that can be used in a web browser. It is written in JavaScript without using any third party libraries and thus does not require additional software installation. The engine uses standard HTML document elements such as div and img. This allows the use of any media format supported by browsers including vector graphics svg, gif animations and css styles.
webview_deno - 🌐 Deno bindings for webview, a tiny library for creating web-based desktop GUIs
caniuse - Raw browser/feature support data from caniuse.com
uBlock-Safari - uBlock Origin - An efficient blocker for Chromium, Firefox, and Safari. Fast and lean.