tangledbytes

{
    "configurations": [
        {
            "name": "Linux",
            "includePath": [
                "${workspaceFolder}/**",
                "${workspaceFolder}/node_modules/node-addon-api",
                "~/.nvm/versions/node/v14.16.0/include/node/**"
            ],
            "defines": [],

kentcdodds

user-package-stats

I was poking around trying to figure out all the packages I have access to publish and got curious. So I write this little script to determine the download stats for all the packages I have publish access to.

Feel free to try it yourself. Just change the username passed to getUserDownloadStats.

By default, the stats are sorted by their average daily downloads (descending). That should give you an idea of the most "popular" package of a given user relative to how long that package has been around.

You can use it with npx like so:

jjsquady

How to setup next.js app on nginx with letsencrypt

next.js, nginx, reverse-proxy, ssl

1. Install nginx and letsencrypt

$ sudo apt-get update
$ sudo apt-get install nginx letsencrypt

Also enable nginx in ufw

jonnymaceachern

for i in *.mp4;
  do name=`echo "$i" | cut -d'.' -f1`
  echo "$name"
  ffmpeg -i "$i" -acodec libvorbis -aq 5 -ac 2 -qmax 25 -threads 2 "${name}.webm"
done

menangen

//
//  main.c
//  testQJS
//
//  Created by menangen on 15/08/2019.
//  Copyright © 2019 menangen. All rights reserved.
//

#include "quickjs.h"
#include "quickjs-libc.h"

gabrielschulhof

const addon = require('bindings')('addon');

addon.receiveModule('fs', require('fs'));
addon.receiveModule('crypto', require('crypto'));

console.log(addon.sendModule('fs') === require('fs'));
console.log(addon.sendModule('crypto') === require('crypto'));

rauschma

// From callbacks to Promises to async functions

function callbackFunc(x, callback) {
  f1(x, (err1, result1) => {
    if (err1) {
      console.error(err1);
      callback(err1);
      return;
    }
    f2(result1, (err2, result2) => {

gabrielschulhof

#include <stdio.h>
#include <node.h>

static void
NativeClassConstructor(const v8::FunctionCallbackInfo<v8::Value>& info) {
}

static void
NativeClassProtoMethod(const v8::FunctionCallbackInfo<v8::Value>& info) {
  fprintf(stderr, "NativeClassProtoMethod was called\n");

gabrielschulhof

#include <stdio.h>
#include <node.h>

class WeakRef {
 public:
  WeakRef(v8::Isolate* isolate, v8::Local<v8::Value> func, const char* string):
      string_(string) {
    pers_.Reset(isolate, func);
    pers_.SetWeak(this, DeleteMe, v8::WeakCallbackType::kParameter);
  }

thlorenz

Summary

Tried to improve debugging when an express middleware is wrapped to auto-handle errors of an asnync function.

Turns out the below reads a bit better than a return Promise.catch() implementation, but still, once we reach the central express error handler, the line of the wrapped function that caused the error isn't included.

Implementation

'use strict'