guest271314

• V8

V8 is Google’s open source high-performance JavaScript and WebAssembly engine, written in C++. It is used in Chrome and in Node.js, among others. It implements ECMAScript and WebAssembly, and runs on Windows 7 or later, macOS 10.12+, and Linux systems that use x64, IA-32, ARM, or MIPS processors. V8 can run standalone, or can be embedded into any C++ application.

• SpiderMonkey

SpiderMonkey is Mozilla’s JavaScript and WebAssembly Engine, used in Firefox, Servo and various other projects. It is written in C++, Rust and JavaScript. You can embed it into C++ and Rust projects, and it can be run as a stand-alone shell. It can also be [compiled](https://bytecodealliance.org/articles/making-javascript-run-fast-on

khalidx

The experience of using Node.JS with TypeScript, ts-node, and ESM is horrible.

There are countless guides of how to integrate them, but none of them seem to work.

Here's what worked for me.

Just add the following files and run npm run dev. You'll be good to go!

package.json

cassus

import type { Paths, I18n, Translate } from "next-translate"

type Tail<T> = T extends [unknown, ...infer Rest] ? Rest : never

export type TranslationsKeys = {
  common: Paths<typeof import("./locales/en/common.json")>
  ["feat-analytics"]: Paths<typeof import("./locales/en/feat-analytics.json")>
  ["feat-participate"]: Paths<
    typeof import("./locales/en/feat-participate.json")
  >

h-jennings

const AudioPrimitiveContext = React.createContext<InterpreterFrom<
  typeof audioMachine
> | null>(null);

export const AudioPrimitiveProvider = ({
  children,
}: {
  children?: React.ReactNode;
}) => {
  const [machine] = React.useState(() => {

DavidWells

/* Using a JavaScript proxy for a super low code REST client */
// via https://dev.to/dipsaus9/javascript-lets-create-aproxy-19hg
// also see https://towardsdatascience.com/why-to-use-javascript-proxy-5cdc69d943e3
// also see https://github.com/fastify/manifetch
// also see https://github.com/flash-oss/allserver
// and https://gist.github.com/v1vendi/75d5e5dad7a2d1ef3fcb48234e4528cb

const createApi = (url) => {
  return new Proxy({}, {
    get(target, key) {

lifeart

// A launch configuration that compiles the extension and then opens it inside a new window
{
	"version": "0.1.0",
	"configurations": [
		{
			"name": "Attach by Process ID",
			"processId": "${command:PickProcess}",
			"request": "attach",
			"resolveSourceMapLocations": null,
			"sourceMaps": true,

rauschma

Cheat sheet: modules

Named exports, named imports, namespace imports

If we put export in front of a named entity inside a module, it becomes a named export of that module. All other entities are private to the module.

//===== lib1.mjs =====
// Named exports

jelhan

import Controller from '@ember/controller';
import { tracked } from '@glimmer/tracking';
import { cached } from 'tracked-toolbox';
import { scheduleOnce } from '@ember/runloop';

const Observers = [];

class Observer {
    tags = [];
    cb = null;

lifeart

'use strict';

const EmberApp = require('ember-cli/lib/broccoli/ember-app');

module.exports = function (defaults) {
  let app = new EmberApp(defaults, {});

  // we need to add emebr-template-compiler into runtime
  app.import('node_modules/ember-source/dist/ember-template-compiler.js');

maxfierke

import { Yieldable } from 'ember-concurrency';
import fetch from 'fetch'; // i.e. ember-fetch. could also use native fetch too.

class FetchYieldable extends Yieldable {
  constructor(url, opts = {}) {
    super(...arguments);
    this.url = url;
    this.opts = opts;
  }