# TypeScript TypeScript is a strongly typed programming language that builds on JavaScript and provides enhanced developer tooling. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## TanStack Charts Introduced with a Framework Agnostic Grammar of Graphics for TypeScript DevFeed: [TanStack Charts Introduced with a Framework Agnostic Grammar of Graphics for TypeScript]() Original publisher: [Read original article]() Author: Daniel Curtis Published: 2026-09-17T05:53:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Library](), [TypeScript](), [Graphics](), [Frameworks](), [React]() Tags: [angular](), [data-visualization](), [development](), [framework](), [graphics](), [introduced](), [library](), [news](), [react](), [react-native](), [tanstack-charts-alpha-introduced](), [typescript](), [visualization](), [vue-js](), [web-development]() ### AI overview TanStack Charts is a new framework-agnostic TypeScript visualization library that uses a grammar-of-graphics approach instead of fixed chart types. It is in Alpha, has about 160,000 weekly downloads, and supports multiple frameworks and environments, though it is not yet stable for production use. ### Source excerpt TanStack Charts is a new, framework-agnostic visualization library for TypeScript. It allows developers to create visualizations by composing various elements instead of using fixed chart types. Currently in Alpha, it has about 160,000 weekly downloads. The library supports multiple frameworks and is designed for a variety of environments, though it is not yet stable for production use. By Daniel Curtis ## What's New in Apollo Client 4.3 DevFeed: [What's New in Apollo Client 4.3]() Original publisher: [Read original article]() Author: Jerel Miller Published: 2026-09-15T12:01:05Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [apollo-client](), [GraphQL](), [TypeScript](), [Cache](), [Code generation]() Tags: [apollo-client](), [cache](), [codegen](), [graphql](), [native](), [typescript]() ### AI overview Apollo Client 4.3 adds native custom scalar support, type-safe cache access, and improved TypeScript handling for incremental GraphQL data. The release also updates generated types and data-state narrowing for deferred fields. ### Source excerpt Apollo Client 4.3 is here: native custom scalar support, type-safe cache access, and more consistent @defer and @stream behavior. See what's new and upgrade today. ## Apollo Client 4.3 adds native custom scalar support and safer TypeScript types DevFeed: [Apollo Client 4.3 adds native custom scalar support and safer TypeScript types]() Original publisher: [Read original article]() Author: Jerel Miller Published: 2026-09-15T12:01:05Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [TypeScript](), [Cache](), [Caching](), [JSON]() Tags: [cache](), [graphql](), [json](), [typescript](), [upgrade]() ### AI overview Apollo Client 4.3 adds native custom scalar integration, type-safe cache access, and improved TypeScript handling for incremental GraphQL data. ### Source excerpt Apollo Client 4.3 is here: native custom scalar support, type-safe cache access, and more consistent @defer and @stream behavior. See what's new and upgrade today. ## Authentication is a long-running Workflow DevFeed: [Authentication is a long-running Workflow]() Original publisher: [Read original article]() Author: Mason Williams Published: 2026-09-15T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Authentication](), [MFA](), [browser](), [Go Language](), [TypeScript](), [Deployment](), [push-notification](), [sessions](), [API]() Tags: [api](), [authentication](), [browser](), [community](), [deployment](), [go](), [mfa](), [push-notification](), [sessions](), [typescript]() ### AI overview This article explains how KERNEL models Managed Auth as a long-running Temporal workflow. A parent workflow maintains connection state, health checks, reauthentication, and cancellation, while child workflows handle individual login attempts with separate browsers, timeouts, and cleanup. Durable state stays in Go, and model-driven work runs in a dedicated TypeScript Worker. ### Source excerpt In this article# - A login is not a request - Model the connection, not the attempt - The human is part of the Workflow - Staying logged in is part of the product - Go owns durability; TypeScript runs the agent - What we learned 1. A login is not a request# An agent can enter a password, stop at an MFA prompt, wait for a person to approve a push notification, and then resume in the same browser. A deployment or Worker restart can happen anywhere in between. ## How to Use Differential Testing During a Legacy Migration DevFeed: [How to Use Differential Testing During a Legacy Migration]() Original publisher: [Read original article]() Author: Hugo Teijiz Published: 2026-09-14T16:25:50Z Content type: tutorial Language: en Sources: [freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More]() Topics: [migration](), [Testing](), [TypeScript](), [Integration testing](), [API](), [observability](), [Artificial Intelligence]() Tags: [ai](), [api](), [architecture](), [artificial-intelligence](), [code](), [how-to](), [integration](), [legacy-code](), [legacy-modernization](), [migration](), [modernization](), [observability](), [software-architecture](), [software-testing](), [testing](), [tests](), [tutorial](), [typescript]() ### AI overview This tutorial explains how to use differential testing during a legacy migration by running old and new implementations with identical inputs and comparing their behavior. It covers equivalence rules, output normalization, nondeterministic values, errors, side effects, automated testing, mismatch analysis, production shadow traffic, and using AI to classify divergences without allowing it to determine correctness. ### Source excerpt The most dangerous moment in a legacy migration isn't necessarily when you start writing the new implementation. It's when the new implementation looks finished. The code compiles, the tests pass, the ## Using modern-web-types to add newer web API types to TypeScript DevFeed: [Using modern-web-types to add newer web API types to TypeScript]() Original publisher: [Read original article]() Published: 2026-09-14T07:22:45Z Content type: tutorial Language: en Sources: [Philip Walton]() Topics: [TypeScript](), [Web](), [Code](), [Library](), [Web Development](), [view transitions]() Tags: [code](), [libraries](), [library](), [typescript](), [view-transitions](), [web]() ### AI overview The article explains why TypeScript reports errors for newer web APIs that are available in Chrome: its built-in web API libraries require support from at least two browser engines. It introduces modern-web-types, a drop-in replacement using a single-engine support threshold, and describes how to install it for web and worker projects. ### Source excerpt If you've ever written code against a new web API in TypeScript, you've probably seen an error telling you the thing you're using doesn't exist. Turns out, TypeScript intentionally doesn't support all new APIs, but there's an easy fix. ## Use Drizzle ORM with Appwrite Postgres DevFeed: [Use Drizzle ORM with Appwrite Postgres]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-09-08T00:00:00Z Content type: tutorial Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Drizzle](), [migration](), [Object-relational mapping](), [PostgreSQL](), [TypeScript](), [Databases](), [SQL]() Tags: [data](), [drizzle](), [migration](), [migrations](), [orm](), [postgres](), [postgresql](), [schema](), [sql](), [tutorials](), [typescript]() ### AI overview A tutorial showing how to connect Drizzle ORM to Appwrite Postgres, define tables and queries in TypeScript, generate and apply SQL migrations, seed data, and evolve a schema while preserving existing records. ### Source excerpt Connect Drizzle ORM to Appwrite Postgres, query data with TypeScript, and apply SQL migrations as your schema changes. ## Use Prisma ORM with Appwrite Postgres DevFeed: [Use Prisma ORM with Appwrite Postgres]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-09-08T00:00:00Z Content type: tutorial Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Prisma](), [Object-relational mapping](), [PostgreSQL](), [migration](), [TypeScript]() Tags: [database](), [migration](), [migrations](), [postgresql](), [prisma](), [schema](), [tutorials](), [typescript]() ### AI overview A practical guide to using Prisma ORM with Appwrite Postgres in a TypeScript project. It covers creating the PostgreSQL database, configuring the connection and TLS settings, defining models, generating and applying migrations, generating Prisma Client, and connecting to the database through a driver adapter. ### Source excerpt Model your data with Prisma ORM, generate a typed client, and test schema migrations against Appwrite Postgres. ## How to Reclaim Excess SOL After Rent Reduction DevFeed: [How to Reclaim Excess SOL After Rent Reduction]() Original publisher: [Read original article]() Author: Solana Foundation Published: 2026-09-03T15:15:00Z Content type: tutorial Language: en Sources: [Solana News Feed]() Topics: [Solana](), [Authorization](), [TypeScript]() Tags: [authorization](), [blockchain](), [blockchain-technology](), [crypto-news](), [cryptocurrency](), [defi](), [developers](), [how-to](), [nfts](), [podcasts](), [solana](), [solana-ecosystem](), [technology](), [token](), [typescript](), [upgrades](), [web3]() ### AI overview This tutorial explains how to reclaim excess SOL caused by Solana rent reductions. It covers withdrawing surplus lamports from token accounts and mints with WithdrawExcessLamports, and implementing similar reclaim logic for program-owned PDAs. ### Source excerpt Rent on Solana has been Reduced. Every Account Is Now Over-Funded. Here's How to Reclaim Excess SOL. ## Checks for safer review of rapidly generated TypeScript and React frontend code DevFeed: [Checks for safer review of rapidly generated TypeScript and React frontend code]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-09-01T00:00:00Z Content type: tutorial Language: en Sources: [Evil Martians]() Topics: [Front end](), [React](), [TypeScript](), [Artificial Intelligence](), [OpenAPI Specification](), [API](), [mutation-testing](), [Testing](), [Code]() Tags: [agent-experience](), [agentic-development](), [agents](), [ai](), [api](), [code](), [continuous-integration](), [dx](), [frontend](), [llms](), [mutation-testing](), [openapi](), [react](), [testing](), [typescript]() ### AI overview This article presents ten checks for making rapidly generated TypeScript and React frontend code safer to trust and cheaper to review. It covers API contracts, generated types, boundary validation, mutation testing, dead-code detection, and mandatory checks. ### Source excerpt Ten checks that catch what AI-written frontend code hides: contract codegen, boundary linting, mutation testing, and dead-code detectors. ## Build a Video API with Twilio Programmable Video, Node.js, TypeScript, and Express DevFeed: [Build a Video API with Twilio Programmable Video, Node.js, TypeScript, and Express]() Original publisher: [Read original article]() Author: Mia Adjei Published: 2026-08-31T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [API](), [Node.js](), [Express](), [TypeScript](), [SDKs]() Tags: [api](), [api-js](), [api-keys](), [api-node](), [api-nodejs](), [api-twilio](), [build](), [build-api](), [developer-insights](), [env-file-security](), [express](), [how-to](), [javascript-api](), [node](), [node-js](), [nodejs](), [nodejs-api](), [tutorial](), [twilio-api](), [twilio-programmable-video](), [typescript](), [use-api-with-javascript](), [video](), [video-api](), [video-javascript](), [video-js]() ### AI overview A tutorial showing how to build an API that creates and manages video rooms programmatically using Twilio Programmable Video, Node.js, TypeScript, and Express. ### Source excerpt Learn how to create and manage video chat rooms programmatically using Twilio Programmable Video and Node.js. ## How the JavaScript Development Stack Is Viewed by the Community in 2026 DevFeed: [How the JavaScript Development Stack Is Viewed by the Community in 2026]() Original publisher: [Read original article]() Author: vostrik ("Лаборатория Касперского") Published: 2026-08-28T08:17:45Z Content type: opinion Language: ru Sources: ["Лаборатория Касперского" RU]() Topics: [TypeScript](), [Git]() Tags: [2026](), [git](), [javascript](), [tag-1e376f0a5f9f](), [tag-39f0c170b680](), [tag-cdf241ba4036](), [typescript]() ### AI overview The article examines the JavaScript ecosystem through a survey of more than 120 engineers at HolyJS Spring 2026. It presents the resulting technology radar as a view of practical engineering choices, emphasizing predictability, delivery speed, scalability, and reduced cognitive load. ### Source excerpt Хайп-цикл фронтенда, кажется, наконец-то выдохся. Мы вышли из фазы бесконечного переизобретения колеса, где каждый месяц появлялся "убийца React", и вошли в эпоху убийцы Fable инженерной зрелости. Сегодня опытного инженера сложно впечатлить очередным фреймворком: ценность сместилась в сторону предсказуемости, скорости поставки (delivery) и снижения когнитивной нагрузки. Привет, меня зовут Павел Востриков, и я -- архитектор веб-направления в "Лаборатории Касперского". В этой статье хочу разобрать JS-экосистему как набор инженерных компромиссов. На HolyJS Spring 2026 мы предложили 120+ инженерам оценить свой реальный стек. Получившийся радар мог быть просто списком библиотек, но в итоге вышел срезом того, как выглядит рациональный подход к коду в 2026 году. Мы видим, как разработчики массово идут в сторону предсказуемой скорости масштабирования решений и инженерной гигиены. Читать далее ## The best API integration platforms for SaaS apps and agents in 2026 DevFeed: [The best API integration platforms for SaaS apps and agents in 2026]() Original publisher: [Read original article]() Author: Emmanuel Published: 2026-08-26T17:40:00Z Content type: comparison Language: en Sources: [Daniel Glejzner]() Topics: [API](), [Angular](), [Software as a service](), [TypeScript](), [SDKs](), [Feathers]() Tags: [2026](), [angular](), [api](), [api-integration](), [apps](), [comparison](), [integration](), [platforms](), [saas](), [sdk](), [typescript]() ### AI overview A comparison of six embedded API integration platforms for SaaS products, focused on Angular and TypeScript teams. It evaluates SDKs, documentation, Angular fit, backend control, customization, API coverage, workflow-building capabilities, and suitability for prototypes or deep integrations. ### Source excerpt A hands-on guide for Angular and TypeScript teams. compared six platforms and focused on how easily each fits into an Angular app and how much backend control you retain when an integration goes beyond the standard flow. ## Building an Operational Ontology: An E-Commerce Walkthrough DevFeed: [Building an Operational Ontology: An E-Commerce Walkthrough]() Original publisher: [Read original article]() Author: Togo YAMANAKA Published: 2026-08-26T14:29:30Z Content type: tutorial Language: en Sources: [Data Engineering Weekly]() Topics: [semantic-layer](), [SQL](), [TypeScript](), [Open Source](), [Databases]() Tags: [customer](), [data-pipeline](), [implementation](), [integration](), [open-source](), [semantic-layer](), [sql](), [typescript]() ### AI overview A walkthrough builds an operational ontology over integrated e-commerce order data from two systems with different schemas and status encodings. It models customers, orders, products, and relationships, then introduces named actions, business rules, and write-back to systems of record. ### Source excerpt The write side of the ontology conversation: named actions, business rules, and write-back to the systems of record -- a pattern already running at enterprise scale. ## Setting up a CI/ CD pipeline with GitLab: Quality, Test and Report DevFeed: [Setting up a CI/ CD pipeline with GitLab: Quality, Test and Report]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-25T02:28:52Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [CI/CD Pipeline](), [GitLab](), [Testing](), [Playwright](), [pull-requests](), [TypeScript]() Tags: [bun-create-playwright](), [ci-cd](), [ci-cd-pipeline](), [code-reviews](), [gitlab](), [playwright](), [test](), [testing](), [typescript](), [workflows]() ### AI overview A tutorial on setting up a three-stage GitLab CI/CD pipeline for merge requests. The pipeline runs code-quality checks, smoke and regression tests, and produces a downloadable report, with stages executed sequentially and jobs within each stage running in parallel. ### Source excerpt So far, we have reviewed how to review code with ES Lint + Prettier and Typecheck, how to set up and run smoke tests, how to run all Playwright + TypeScript tests, and reviewed the HTML report of results. In this post, we are going to set up a three stage GitLab CI/ CD pipeline that will run against every merge request: Quality (lint, typecheck, prettier) --> Test ( smoke + regression ) --> Report ( Downloadable ) I haven't used GitLab since when I worked at ThreatStack back in 2020. ( See my blog entry Getting to Know GitLab and How They Test the UI ) GitLab reads .gitlab-ci.yml from the repository root and turns it into a pipeline, a set of jobs, grouped into stages, running whenever you push a change to a repository. Stages run one after another, and jobs within a stage run in parallel. If one stage fails, the stages after it are skipped. This begs the question: What is GitLab? What is CI/ CD? Or a pipeline? Or a merge request? What is GitLab? GitLab began in 2011 as a side project by Ukrainian programmer Dmytro Zaporozhets, built to help developers work together on code more easily. Over time, it grew into a large open-source DevOps platform. More than just storing code, it handles code reviews, CI/CD (continuous integration and continuous delivery), and package registries. A company called GitLab Inc. was eventually created to turn the project into a commercial product. What makes GitLab different from tools that only host Git repositories (like a basic Git server) is that it bundles the entire software delivery process into one application. This includes: Merge requests - GitLab's term for proposing and reviewing code changes before they're merged into the main codebase (similar to a "pull request" in GitHub) Issue tracking - a built-in system for logging bugs, tasks, and feature requests Pipelines - automated workflows that build, test, and deploy code whenever changes are pushed So instead of stitching together separate tools for version control, testing, an ## How Lovable Migrated lovable.dev from Next.js to TanStack Start DevFeed: [How Lovable Migrated lovable.dev from Next.js to TanStack Start]() Original publisher: [Read original article]() Author: Alexandre Zajac Published: 2026-08-24T15:30:50Z Content type: article Language: en Sources: [Hungry Minds]() Topics: [Next.js](), [Development](), [Software Engineering](), [dogfooding](), [Vercel](), [TypeScript]() Tags: [adapter-pattern](), [development](), [dogfooding](), [framework](), [next-js](), [software-engineering](), [trends](), [typescript](), [vercel]() ### AI overview The article describes Lovable's migration of lovable.dev from Next.js on Vercel to TanStack Start. It outlines a gradual rollout using parallel routing and feature flags, route grouping, shared framework-agnostic code, adapters, and AI-assisted migration. ### Source excerpt PLUS: Semantic layer at PostHog 🏗, AliExpress fingerprinting 🔎 , Git serving rebuilt at Datadog 📈 ## Develop and test MCP in Postman: jhipster-mcp in action DevFeed: [Develop and test MCP in Postman: jhipster-mcp in action]() Original publisher: [Read original article]() Author: Anthony Viard Published: 2026-08-19T16:00:00Z Content type: article Language: en Sources: [Postman Blog]() Topics: [Model Context Protocol](), [Postman](), [Spring Boot](), [Node.js](), [TypeScript](), [Angular](), [React](), [Vue.js](), [JSON](), [Remote Procedure Call (RPC)]() Tags: [ai-agents](), [angular](), [apache](), [cli](), [general](), [jhipster](), [json](), [mcp](), [node-js](), [open-source](), [post](), [react](), [rpc](), [spring-boot](), [typescript](), [vue]() ### AI overview This Postman developer article demonstrates jhipster-mcp, an open-source MCP server that exposes the JHipster generator to MCP clients. It uses Postman's MCP client to test tools, prompts, and resources for generating and evolving Spring Boot applications from JDL. ### Source excerpt Drive the jhipster-mcp server from Postman's MCP client to test tools, prompts, and resources before handing them to an AI agent. Try it today. The post Develop and test MCP in Postman: jhipster-mcp in action appeared first on Postman Blog. ## How Omit Can Collapse TypeScript Union Types into an Empty Object DevFeed: [How Omit Can Collapse TypeScript Union Types into an Empty Object]() Original publisher: [Read original article]() Author: Zlaylink (Яндекс) Published: 2026-08-19T07:23:14Z Content type: tutorial Language: ru Sources: [Яндекс - Как мы делаем Яндекс / Статьи]() Topics: [TypeScript](), [ide]() Tags: [distributive](), [ide](), [omit](), [tag-39f0c170b680](), [typescript]() ### AI overview This tutorial explains how applying TypeScript's Omit utility to union types can produce an empty object type instead of preserving each union branch. Using a user-data example and event interfaces, it describes how this can remove useful type checking and autocomplete, and introduces type distributivity as the underlying concept. ### Source excerpt Представьте ситуацию: вы выкатываете новую фичу, а бэкендер спрашивает вас: "Слушай, а почему вместо событий -- пустой объект?". Вы в шоке: "Как так -- пустой объект? У меня же TypeScript, всё типизировано, такого не могло быть!". Спойлер -- могло. Меня зовут Денис Платонов, я старший разработчик интерфейсов в Телемосте и я отвечаю за on-premise развёртывание веб-клиента Телемоста в инфраструктуре заказчика. В этой статье я расскажу о том, как безобидный на первый взгляд Omit превратил наш аккуратный тип событий в пустой объект. Заодно разберём, как работает дистрибутивность типов в TypeScript и поделимся, чему нас научил этот кейс. Читать далее ## Anders Hejlsberg on Rewriting the TypeScript Compiler in Go DevFeed: [Anders Hejlsberg on Rewriting the TypeScript Compiler in Go]() Original publisher: [Read original article]() Author: Ryan Peterman Published: 2026-08-17T13:03:31Z Content type: opinion Language: en Sources: [The Developing Dev]() Topics: [TypeScript](), [Compiler](), [Go Language](), [Artificial Intelligence](), [Software Engineering]() Tags: [ai](), [compiler](), [go](), [podcasts](), [software-engineering](), [typescript]() ### AI overview A podcast interview with Anders Hejlsberg discusses the decision to rewrite the TypeScript compiler in Go, the limited use of LLMs during the rewrite, and his views on AI's impact on software engineering. ### Source excerpt It was interesting talking to Anders Hejlsberg, the creator of TypeScript and C#, about all the technical details behind rewriting the TypeScript compiler in Go. ## Neon for Herdr: A Neon pane in your Herdr workspace DevFeed: [Neon for Herdr: A Neon pane in your Herdr workspace]() Original publisher: [Read original article]() Author: Dominik Koch Published: 2026-08-13T12:00:00Z Content type: release Language: en Sources: [Blog -- Neon Docs]() Topics: [SDKs](), [TypeScript](), [Terminal](), [dashboards](), [OAuth](), [Databases](), [autoscaling](), [Command-line interface]() Tags: [autoscaling](), [browser](), [community](), [databases](), [linux](), [macos](), [oauth](), [typescript]() ### AI overview Neon for Herdr is a terminal workspace plugin that adds a Neon project-management pane built with Ink, Effect, and the Neon TypeScript SDK. It supports project and branch operations, compute controls, connection-string retrieval, fuzzy search, and OAuth authentication with PKCE. ### Source excerpt I just released Neon for Herdr, a Herdr plugin that puts your Neon projects in a pane next to whatever you are already doing, so creating a branch, grabbing its connection string, or suspending a compute is only a keypress away. ## The SvelteKit 3 Release Candidate is here DevFeed: [The SvelteKit 3 Release Candidate is here]() Original publisher: [Read original article]() Author: The Svelte team Published: 2026-08-13T00:00:00Z Content type: release Language: en Sources: [Svelte blog]() Topics: [Svelte](), [migration](), [Code](), [configuration](), [TypeScript](), [App]() Tags: [code](), [dev](), [documentation](), [feature](), [guide](), [migration](), [release](), [svelte](), [typescript]() ### AI overview SvelteKit 3 has reached the release candidate phase, introducing breaking changes from SvelteKit 2 alongside migration tooling, updated configuration in vite.config.ts, and a shift from the $lib alias to Node subpath imports. ### Source excerpt SvelteKit 3 is now in the Release Candidate phase. If all goes well -- meaning that people like you try it out and find that it works as expected -- we will follow it up with a stable release in the near future, with no further breaking changes. But there are some breaking changes since SvelteKit 2. We're taking advantage of this release to prune some of the weeds in the codebase and lay the groundwork for SvelteKit's continued evolution, more on which below. To migrate an existing app, you can use the next version of sv migrate: npx sv@next migrate sveltekit-3 --tasks all --confirm This will automatically migrate as much of your code as possible. For everything else, it will generate a TODO list for you (or your clanker of choice) to work through. Wherever possible, SvelteKit will print useful diagnostic warnings and errors if you try to run code that hasn't yet been updated. To create a new app, run sv create: npx sv@next create my-new-app What's changed? For the full list of changes, consult the migration guide over on next.svelte.dev which is where the SvelteKit 3 documentation will live until the stable release. Most changes are fairly minor, but a few are worth calling out: Configuration now lives in vite.config.ts Previously, you would configure SvelteKit via a svelte.config.js file. This turned out to be limiting: it's useful for the Vite plugin to have access to your config immediately rather than having to go through an asynchronous resolution process (which can't begin until after we've resolved the entire Vite config, because tools like Vitest may run with a current working directory that isn't the project root), and after all why wouldn't we put the config in one place rather than two? The $lib alias is now #lib In SvelteKit 2, you would put shared code in src/lib and import it via a $lib alias. This is nicer than importing from ../../../../somewhere, which is what inevitably happens in larger codebases. But in modern projects, aliases are unnecessary, be ## Add Type Checking and TSConfig to Bun-Create-Playwright DevFeed: [Add Type Checking and TSConfig to Bun-Create-Playwright]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-08T03:10:43Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [Bun](), [TypeScript](), [Playwright](), [Compiler](), [Code](), [Command-line interface]() Tags: [bun](), [bun-create-playwright](), [code](), [compiler](), [playwright](), [terminal](), [typescript]() ### AI overview This tutorial adds TypeScript type checking and tsconfig configuration to a Bun-Create-Playwright project. It explains why Playwright should be run alongside the TypeScript compiler and demonstrates using tsc --noEmit to check code without emitting output files. ### Source excerpt Now that we have installed bun, Anthropic's package manager, and scaffolded a Playwright framework and closely examined the results, we are going to explore with our Bun-Create-Playwright project ways to check if our code is correct. The first method we will be exploring is typechecking. Why Typechecking? As the Playwright.dev / Node.js Introduction mentions: "[...] Playwright does not check the types and will run tests even if there are non-critical TypeScript compilation errors. We recommend you run TypeScript compiler alongside Playwright. "[...] Note that Playwright only supports the following tsconfig options: allowJs, baseUrl, paths, references and extends. "[...] By default, Playwright will look up a closest tsconfig for each imported file by going up the directory structure and looking for tsconfig.json or jsconfig.json. This way, you can create a tests/tsconfig.json file that will be used only for your tests and Playwright will pick it up automatically".Before we go further down this road... What is Type Checking? According to Type Checking in TypeScript: A Beginners Guide, every piece of data in TypeScript is given a "type", and this "type" determines what properties the data has, and what methods are available to it. The types can be things like a Number, String, Enum, Boolean, Array, Object, Type assertions, or others. Since all data in TypeScript is given a type, it means that the TypeScript compiler, tsc, can check every property to make sure it is being used correctly. It makes sure that the expected properties exist and that the methods and functions are all compatible. And best of all, you can run these checks in your IDE as you are writing the code! To run typechecking against our code, all we have to do is execute from the Terminal: tsc --noEmit Since we are just kicking the tires of our code to see what happens, we don't need to emit "compiler output files like JavaScript source code, source-maps or declarations. This makes room for another tool ## Scaffold and Run Playwright Tests with Bun DevFeed: [Scaffold and Run Playwright Tests with Bun]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-06T17:37:06Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [Playwright](), [Bun](), [Node.js](), [TypeScript](), [Windows]() Tags: [bun](), [bun-create-playwright](), [playwright](), [test](), [typescript](), [windows]() ### AI overview A tutorial on creating a TypeScript Playwright project with Bun, installing its browsers on Windows, configuring a Bun lockfile and test script, and running the included tests. It notes that Playwright's test runner remains a Node.js program and documents an additional Bun and Playwright installation step for a Windows bug. ### Source excerpt We covered in the last blog post how to install bun, a new package manager. In this blog post, we will look into using bun to install a new Playwright framework. Create the Playwright Framework Once I installed bun on my Windows PC and was up and running I created a new folder, "bun-create-playwright". I opened up that folder in VS Code, along with a new PowerShell terminal. In that terminal I entered: bun create playwright This activated the interactive Playwright installer that Playwright comes with. I selected I wanted it to create for me a TypeScript project, placing the tests in the default folder, tests, but I decided not to add a GitHub Actions workflow. I wanted to experiment with using GitLab. I chose it to set up and install all the browsers for me... which it did... using NPX, part of Node. Wait a second, when it comes to our Playwright framework, doesn't bun replace node? No. Bun might be a JavaScript runtime, a package manager, and a bundler shipped as a single software tool, but in our case we are simply using it as a package manager in our Playwright framework. Bun works alongside Node.js in the Playwright project. We still use Playwright's test runner, a Node.js program. Bun handles installations and run tasks. Alert: Windows Bug! Initially, that wasn't enough to install Playwright's internal browsers. There is a bug with bun + Playwright Windows where we also need to: bun add --dev @playwright/test bunx playwright install That was enough for the browsers to install. Create the Bun Lock File After the browsers are installed, we need to install bun in our project, to create from the package.json a bun installation. Run in the Terminal: bun install Review the newly created file bun.lock.file in the root directory of the project. Delete the package-lock.json file. Add the test script to the Package.json If you look in the package.json file, you can see that the scripts code block is currently empty. "scripts": {} Inside this code block, we will be addin ## Next.js 16.3 brings client-side caching to the App Router DevFeed: [Next.js 16.3 brings client-side caching to the App Router]() Original publisher: [Read original article]() Author: Aditya Oberai Published: 2026-08-05T00:00:00Z Content type: article Language: en Sources: [Appwrite Blog]() Topics: [Next.js](), [Caching](), [Server-side rendering](), [TypeScript](), [Node.js](), [Vercel]() Tags: [caching](), [news](), [next-js](), [performance](), [ssr](), [typescript](), [upgrade](), [vercel]() ### AI overview This article explains the Next.js 16.3 release, focusing on client-side caching and SPA-style navigation for the App Router through the opt-in Instant Navigations suite. It also covers performance changes including reduced development-server memory usage, cached builds, faster TypeScript checking, and increased request handling under load. ### Source excerpt Next.js 16.3 lands with client-side caching, up to 90% less dev server memory, disk cached builds, and opt-in Instant Navigations. Here is how to upgrade. [Next page]()