completions VS name-needed

I am building _exactly_ the same thing for Playwright over at https://ray.run/. I think this is the future of writing tests no doubt. Planning to launch next week.

Note: Use page.goto('/') and have "baseURL": "http://ray.run" set in the playwright.config.ts file for concise code.

Your website https://ray.run/ does have that nostalgic early 2000s vibe, which is cool! Regarding the search functionality, you might want to explore open-source alternatives to Algolia.

Projects like Elasticsearch, Solr, or even using Google Custom Search can provide search capabilities without the cost. They might require a bit more setup and maintenance, but they can be budget-friendly options for a free community.

In case you need help or assistance with your project, feel free to contact us! https://www.ratherlabs.com

* Most of the pages I use are rendered at the request time, rather than build time

For context, this is the website https://ray.run/

Ensuring in-article hover definitions for terms on the https://ray.run/ blog.

I have added a zone to Cloud DNS (GCP) for https://ray.run/

I updated completions library to allow statically typed responses:

import { type Browser, chromium, test as base } from '@playwright/test'; import getPort from 'get-port'; import { playAudit } from 'playwright-lighthouse'; export const test = base.extend<{}, { browser: Browser; port: number }>({ browser: [ async ({ port }, use) => { const browser = await chromium.launch({ args: [`--remote-debugging-port=${port}`], }); await use(browser); await browser.close(); }, { scope: 'worker' }, ], port: [ // eslint-disable-next-line no-empty-pattern async ({}, use) => { // Assign a unique port for each playwright worker to support parallel tests const port = await getPort(); await use(port); }, { scope: 'worker' }, ], }); test.describe('Accessibility Testing with Lighthouse', () => { test('should pass the Lighthouse accessibility audit', async ({ page, port, }) => { await page.goto('https://ray.run/'); await playAudit({ page, port, thresholds: { accessibility: 100, }, }); }); });

import { test } from '@playwright/test' test.beforeEach(async ({ page }) => { await page.goto('https://ray.run/login') await page.fill('#username', 'admin') await page.fill('#password', 'password123') await page.click('#login-button') expect(await page.url()).toContain('/dashboard') }) test('should display user profile', async ({ page }) => { await page.click('#profile-button') expect(await page.textContent('body')).toContain('Admin User') }) // Other tests...

For my long term side project I just dump ideas into a barely organised backlog.md [^1]. After finishing a feature or taking a few months away, I normally dive back in by browsing this and choosing the next milestone.

It's worked well for a couple of years, and helps me keep the long term goals in mind.

[^1] https://github.com/DomWilliams0/name-needed/blob/develop/.pl...

https://domwillia.ms

It uses a custom static site generator because I needed to procrastinate somehow before starting the first post... Now it's nicely stable and punishing new posts is quick and easy

Location: Tallinn, Estonia (UK citizen intending to move there)

Remote: Willing to work partly remote but I require a sponsored visa to work in Estonia

Willing to relocate: Yes, to Tallinn :^)

Technologies: Rust, C, Python preferably, but C++ too. I enjoy low-level work focused on performance; see my toy OS, JVM implementation and game engine on my github profile.

Résumé/CV: https://domwillia.ms | https://github.com/DomWilliams0 | please reach out via email for my résumé

Email: [email protected]

I've written some pretty low-level OpenGL bindings in Rust, because the existing solutions are either too high level or over the top complexity wise.

At the time I only had experience with the OpenGL C api and didn't want to learn a totally different Rust abstraction or mix C/C++ libraries into a pure Rust project.

https://github.com/DomWilliams0/name-needed/tree/develop/ren...

I've been alternating between two long term Rust projects, which seems to work in keeping the motivation up for both!

A Dwarf Fortress-like game (and engine): https://github.com/DomWilliams0/name-needed

A x64 operating system: https://github.com/DomWilliams0/DomeOS

A Dwarf Fortress-like game (and engine) in Rust: https://github.com/DomWilliams0/name-needed

Ambitious to be sure, but after a year and a half I'm still consistently working on it, and still enjoying it!