SkiaSharp VS Playwright

It looks like the port was compiled with a binary SkiaSharp [0] since that requires Google tooling to build. Interesting to see the committer allowing this. Apparently it is not the first time.

0. https://github.com/mono/SkiaSharp

The library that I've had the best luck with is SkiaSharp with .net 3.1. That said, I agree with others that I'd update the version of .net if possible.

Found this issue that basically say it's not supported in skia directly, and it's right, from this page it seems only supported on iOS/Mac. This is pretty frustrating considering the documentation of SkiaSharp Encode() doesn't mention it.

Yes, I'm not aware of any way to use either the canvas api or webgl directly. This project has bindings for the canvas API, but it hasn't been updated in two years:https://github.com/BlazorExtensions/Canvas. SkiaSharp seems a nice option too: https://github.com/mono/SkiaSharp. It supports graphics across a whole load of platforms, including Blazor on the web.

If you want pure .NET, cross-platform, and future compatibility, SkiaSharp is the new way to do it.

This seems to be a clash with skiasharp. The other package I have which uses skiasharp is Mapsui Possibly related to this issue with SkiSharp mono/SkiaSharp#1879

This is interesting since SkiaSharp says:

The consensus I could gather is either use playwright or use a workaround to solve it in the puppeteer layer. The root cause of the bug is a websocket size limitation on the CDP protocol for chromium.

With the advent of tools like Puppeteer and now Playwright, end-to-end testing has become much easier and more reliable. For anyone who's used Selenium in the past, you know what I'm talking about. Puppeteer has opened the way in terms of E2E tooling, but Playwright has taken it to the next level and made it easier to await for certain selectors or conditions to be fulfilled (via locators), thus making tests more reliable and less flaky. Also, it's a game changer that it introduced a test-runner - this made the integration between the headless browser and the actual test code much smoother.

In this tutorial, our main focus will be on Playwright web scraping. So what is Playwright? It’s a handy framework created by Microsoft. It's known for making web interactions more streamlined and works reliably with all the latest browsers like WebKit, Chromium, and Firefox. You can also run tests in headless or headed mode and emulate native mobile environments like Google Chrome for Android and Mobile Safari.

// playwright.config.ts import { defineConfig } from "@playwright/test"; /** * See https://playwright.dev/docs/test-configuration. */ export default defineConfig({ testDir: "./src/pages", reporter: "list", use: { baseURL: "http://localhost:5432/", }, timeout: process.env.CI ? 10000 : 4000, // ... more options });

Issues with Playwright

Fast and reliable end-to-end testing for modern web apps | Playwright

This means you cannot place test files outside of this directory, which was brought up as a question on Github some time ago. Initially, I thought it would be nice to add another folder in the repo called "scripts", but Playwright does not allow multiple testDir values.

4.Playwright: Playwright is a browser automation library by Microsoft. Key Features: Supports Chromium, Firefox, and WebKit. Provides cross-browser testing capabilities. Allows automating web, mobile, and desktop applications

HTML to PDF conversion is a common requirement in modern web applications. It allows users to save web pages, reports, and other content in a format that is easy to share and print. There are many libraries and services available for converting HTML to PDF, each with its own strengths and weaknesses. In this article, we will compare some of the most popular HTML to PDF renderers in Node.js, including Puppeteer, Playwright, node-html-pdf, and Onedoc.

Playwright [ https://playwright.dev/ ] ✅