| # Node.js Structured Logging API - RFC | |
| **Author:** @mertcanaltin | |
| **Status:** REVIEW | |
| **Date:** 2025-01-22 | |
| **Issue:** [#49296](https://github.com/nodejs/node/issues/49296) | |
| --- | |
| ## Summary |
Relax, I only have one Sunday to work on idea, literally my weekend project. So I tried Deepseek to see if it can help. Surprisingly, it works and it saves me another weekend...
Just chat.deepseek.com (cost = free) with prompts adapted from this gist.
| // Inspired from: | |
| // https://ben.akrin.com/driving-a-28byj-48-stepper-motor-uln2003-driver-with-a-raspberry-pi/ | |
| // https://gist.github.com/wolli2710/9ae48c9f39737896c1f6 | |
| const { Gpio } = require("onoff"); | |
| const in1ToGpio = 17; // IN1 | |
| const in2ToGpio = 18; // IN2 | |
| const in3ToGpio = 27; // IN3 | |
| const in4ToGpio = 22; // IN4 | |
| const timeout = 1; // milliseconds |
Most APIs which accept binary data need to ensure that the data is not modified while they read from it. (Without loss of generality, let's only analyze ArrayBuffer instances for now.) Modifications can come about due to the API processing the data asynchronously, or due to the API processing the data on some other thread which runs in parallel to the main thread. (E.g., an OS API which reads from the provided ArrayBuffer and writes it to a file.)
On the web platform, APIs generally solve this by immediately making a copy of the incoming data. The code is essentially:
function someAPI(arrayBuffer) {
arrayBuffer = arrayBuffer.slice(); // make a copy
The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.
This means you have the following choices:
import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.await import(…) from CommonJS instead of require(…).There's the pervarsive notion that all JS is created equal and that there's only minor and easily detectable differences between the various file formats used to author JavaScript. This is correct, from a certain point of view.
For many people writing JavaScript that gets passed into build tools,
| import { Base64 } from 'js-base64' | |
| import { Op } from 'sequelize' | |
| import { fromGlobalId } from 'graphql-relay' | |
| // https://github.com/graphql/graphql-relay-js/issues/94#issuecomment-232410564 | |
| const effectiveOrder = ({ last }, orderBy) => { | |
| /* adds `id ASC` to end of `ORDER BY` if `id` is not already in the `ORDER BY` clause | |
| flips `ASC` to `DESC` (and vice-versa) if pagination arg `last` is defined | |
| */ |
Last updated March 13, 2024
This Gist explains how to sign commits using gpg in a step-by-step fashion. Previously, krypt.co was heavily mentioned, but I've only recently learned they were acquired by Akamai and no longer update their previous free products. Those mentions have been removed.
Additionally, 1Password now supports signing Git commits with SSH keys and makes it pretty easy-plus you can easily configure Git Tower to use it for both signing and ssh.
For using a GUI-based GIT tool such as Tower or Github Desktop, follow the steps here for signing your commits with GPG.
