Since my last post about shiki was really long and described a really deep way on how to use and modify shiki, this is the complete opposite. This shows just short and simple how to use shiki in your eleventy (11ty) project.

A compiled list of linting rules to specifically help you with writing asynchronous code in JavaScript and Node.js.

What I want to do is console.log variables when I create shortcodes. Template fills up the console too much, so it's hard to debug. Wondering whether it's possible to debug with VS code built in debugger. If yes, what's the configuration...

Semver: A Primer

Prefixing a single semver version string with the ^ character defines a range of acceptable versions that include all patch and minor versions from the ones specified up to, but not including, the next version. So "^1.2.3" can be approximately expanded as ">=1.2.3 <2.0.0".

Unlike ~, the ^ operator with a major version of 0 is essentially a no-op, in that it translates to exactly that version rather than a full range. So "^0.2.3" is equal to just "0.2.3" and no more.

One of the more difficult problems with writing systems that communicate over the network is managing input and output—that is, the reading and writing of data to and from the network and hard drive. Moving data around takes time, and scheduling it cleverly can make a big difference in how quickly a system responds to the user or to network requests.

In such programs, asynchronous programming is often helpful. It allows the program to send and receive data from and to multiple devices at the same time without complicated thread management and synchronization.

Avoiding a test count seems to be the trend in Perl modules these days. After all, automated test libraries in other languages don’t have anything similar, and they seem to get by fine. If the test fails in the middle, that can be detected by a non-zero exit code. It’s always felt like annoying bookkeeping, so why bother?

For simple tests like the above, I think that’s fine. Failing with a non-zero exit code has worked reliably for me in the past.

However, there’s one place where I think TAP had the right idea way back in 1988: event driven or otherwise asynchronous code. Systems like this have been popping up in Perl over the years, but naturally, it’s Node.js that has built an entire ecosystem around the concept. Here’s one of my tests that uses a callback system:

In this article, we’ll look at the development of desktop applications using NW.js and Electron, the ups and downs of building one and living with one, using one code base for the desktop and the web, and more.

e simple. Try Codeship for free. Setup o