Twitter

Yesterday I found an interesting sorting problem to work on. The solution involved a SortedDictionary and an ICompa… https://t.co/4x4nfqcFhm

3 days ago

Follow

Hallo @staatsbosbeheer, er ligt hier een koe met een gaatje. Wellicht goed om even polshoogte te nemen. https://t.co/NrmcaXyiuR

1 month ago

Follow

Hi @TheShufflehound, thanks for the beautiful Gillion and Jevelin themes! They are most useful. Are you still developing new themes?

1 month ago

Follow

Reading up on TLS and the beatings it has taken in the past decade 🥊. https://t.co/Jr84euQX5r

2 months ago

Follow

Categories

Tag: TypeScript

JavaScript, Node.js, TypeScript

Support both Node.js and browser JS in one TypeScript file

TypeScript allows for better JavaScript development. JavaScript is getting useful in more domains. But different systems require different ways of handling modules and exposing features. TypeScript solves this by compiling differently when a target is specified.

But what if you need a TypeScript script that supports both vanilla browser JS and Node.js? What if you need to expose 10+ classes?

JavaScript, Node.js, TypeScript

Convert QUnit test to Mocha / Chai

Recently I’ve been playing around with NPM. I switched my unit tests from QUnit to Mocha. This was not as straight forward as one would hope. In this blog I’ll show some example code. At the end I’ll link to a side by side comparison of the entire test project. Hopefully it helps you to convert your code. I’ll be using the Chai BDD assertion engine.

TypeScript

Strongly Typed Events 0.3.0 – now with Signals

Turns out that I needed an even smaller type of event: the signal. It is an event that has no data; it just fires. The Strongly Typed Events project started with the IEvent event that was styled after .Net. Then the ISimpleEvent was added in 0.2.0, for scenarios when no sender is necessary. Now I’ve added the ISignal to version 0.3.0.