<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:webfeeds="http://webfeeds.org/rss/1.0">
  <channel>
    <title>Guido Flohr - #TypeScript</title>
    <description></description>
    <link>https://www.guido-flohr.net/</link>
    <webfeeds:cover image="http://www.guido-flohr.net/assets/images/gfl-profile.jpeg" />
    <atom:link href="https://www.guido-flohr.net/" rel="self" type="application/rss+xml"/>

    <pubDate>Fri, 24 Oct 2025 09:17:45 +0000</pubDate>
    <lastBuildDate>Fri, 24 Oct 2025 09:17:45 +0000</lastBuildDate>
    <generator>Qgoda vv0.11.0 (https://www.qgoda.net/)</generator>
      
      <item>
        <title>Pitfalls in Testing NestJS Modules using HttpService</title>
        <description>&lt;img src="/assets/images/testing-the-nestjs-http-service/man-working-with-hardware.jpeg" width="100%"&gt;In this blog post, we will delve into the challenges developers face when testing NestJS modules utilizing HttpService from @nestjs/axios and explore the crucial role played by the RxJS TestScheduler in overcoming these hurdles. Additionally, we will unravel the intricacies of injecting HttpService into the test module, providing you with a comprehensive guide to fortify your testing strategies and ensure the robustness of your NestJS applications.</description>
        <pubDate>Sat, 27 Jan 2024 22:00:00 +0000</pubDate>
        <link>https://www.guido-flohr.net/testing-the-nestjs-http-service/index.html</link>
        <guid isPermaLink="true">https://www.guido-flohr.net/testing-the-nestjs-http-service/index.html</guid>
        
        <category>Observables</category>
        
        <category>Observers</category>
        
        <category>RxJS</category>
        
        <category>Development</category>
        
        <category>NestJS</category>
        
        <category>Jest</category>
        
        <category>TypeScript</category>
        
        <category>JavaScript</category>
        
        
        <category>Development</category>
        
      </item>
      
      <item>
        <title>Standalone Angular Tour Of Heroes</title>
        <description>The popular Angular Tutorial Tour of Heroes currently does not work as described with recent Angular versions (Angular 18) because the Angular command-line tool now creates a standalone Angular app by default. You could avoid these problems by creating a non-standalone app but it is also quite instructive to just fix the problems yourself and stick with the standalone version.</description>
        <pubDate>Wed, 27 Mar 2024 22:00:00 +0000</pubDate>
        <link>https://www.guido-flohr.net/standalone-angular-tour-of-heroes/index.html</link>
        <guid isPermaLink="true">https://www.guido-flohr.net/standalone-angular-tour-of-heroes/index.html</guid>
        
        <category>Angular</category>
        
        <category>Development</category>
        
        <category>TypeScript</category>
        
        <category>JavaScript</category>
        
        
        <category>Development</category>
        
      </item>
      
      <item>
        <title>Lerna Mono Repos with Internal Dependencies</title>
        <description>&lt;img src="/assets/images/lerna-mono-repos-with-internal-dependencies/lerna.jpeg" width="100%"&gt;Mono repos are very popular nowadays for bundling a collection of related JavaScript libraries in one single repository. Figuring out how to handle dependencies between multiple packages inside that repository was a little tricky for me. This is how I got it working.</description>
        <pubDate>Fri, 11 Sep 2020 21:00:00 +0000</pubDate>
        <link>https://www.guido-flohr.net/lerna-mono-repos-with-internal-dependencies/index.html</link>
        <guid isPermaLink="true">https://www.guido-flohr.net/lerna-mono-repos-with-internal-dependencies/index.html</guid>
        
        <category>TypeScript</category>
        
        <category>JavaScript</category>
        
        <category>Development</category>
        
        
        <category>Development</category>
        
      </item>
      
      <item>
        <title>Yargs 18 Pitfalls</title>
        <description>&lt;img src="/assets/images/yargs-18-pitfalls/pirate-ship.webp" width="100%"&gt;Upgrading Yargs from version 17 to 18 in a TypeScript project using Jest turned out to be a bit of a nightmare. The release notes for Yargs 18.0.0 include the line “yargs is now ESM first” — a seemingly small change that can cause major headaches. In this blog post, we’ll take a closer look at what that means and how to deal with it.</description>
        <pubDate>Tue, 07 Oct 2025 21:00:00 +0000</pubDate>
        <link>https://www.guido-flohr.net/yargs-18-pitfalls/index.html</link>
        <guid isPermaLink="true">https://www.guido-flohr.net/yargs-18-pitfalls/index.html</guid>
        
        <category>Yargs</category>
        
        <category>Jest</category>
        
        <category>Development</category>
        
        <category>TypeScript</category>
        
        <category>JavaScript</category>
        
        
        <category>Development</category>
        
      </item>
      
      <item>
        <title>Dynamic Angular Configuration</title>
        <description>&lt;img src="/assets/images/dynamic-angular-configuration/angular-chameleon.jpeg" width="100%"&gt;Angular apps traditionally rely on static configuration through environment files, necessitating separate builds for each environment &amp;dash; a cumbersome process in practical scenarios. In this blog post, we describe an alternative, where configuration is loaded dynamically at runtime, streamlining development and enhancing flexibility. As an additional benefit, we will validate the configuration against a schema and add type-safety to it.</description>
        <pubDate>Wed, 15 May 2024 21:00:00 +0000</pubDate>
        <link>https://www.guido-flohr.net/dynamic-angular-configuration/index.html</link>
        <guid isPermaLink="true">https://www.guido-flohr.net/dynamic-angular-configuration/index.html</guid>
        
        <category>Angular</category>
        
        <category>Development</category>
        
        <category>Deployment</category>
        
        <category>TypeScript</category>
        
        <category>JavaScript</category>
        
        
        <category>Development</category>
        
      </item>
      
  </channel>
</rss>
