conartist6

import { AST as T } from 'regexpp';

export type Expression = T.Pattern | T.Group | T.CapturingGroup | T.LookaroundAssertion;

export type Visit<R> = (node: T.Node) => R;

export interface Visitors<R> {
  RegExpLiteral?: (node: T.RegExpLiteral, visit: Visit<R>) => R;
  Pattern?: (node: T.Pattern, visit: Visit<R>) => R;
  Alternative?: (node: T.Alternative, visit: Visit<R>) => R;

conartist6

2c2,4
< WhatsApp Inc. (“WhatsApp,” “our,” “we,” or “us”) provides messaging, Internet calling, and other services to users around the world. Please read our Terms of Service so you understand what’s up with your use of WhatsApp. You agree to our Terms of Service (“Terms”) by installing, accessing, or using our apps, services, features, software, or website (together, “Services”).
---
> If you live in the European Region, WhatsApp Ireland Limited provides WhatsApp to you under this Terms of Service and Privacy Policy.
> 
> WhatsApp LLC (“WhatsApp,” “our,” “we,” or “us”) provides messaging, Internet calling, and other services to users around the world. Please read our Terms of Service so you understand what’s up with your use of WhatsApp. You agree to our Terms of Service (“Terms”) by installing, accessing, or using our apps, services, features, software, or website (together, “Services”).
56c58
< Forum and Venue. If you are a WhatsApp user located in the United States or Canada, the “Special Arbitration Provi

conartist6

# EditorConfig is awesome: http://EditorConfig.org

root = true

[*]
end_of_line = lf
insert_final_newline = true

[{*.{js,json,md}}]
charset = utf-8

conartist6

const { join, normalize, dirname, relative } = require('path');
const { sync: readPkgUp } = require('read-pkg-up');

function pkgname(path) {
  const match = /(^@?[^/]+\/[^/]+|[^/]+)(.*)/.exec(path);
  return match && [match[1], match[2]];
}

const pkg = readPkgUp({ normalize: false });
const root = dirname(pkg.path);

conartist6

function* range(end) {
  for (let i = 0; i < end; i++) {
    yield i;
  }
}

const a = Array.from(range(65536));

module.exports['for await..of values from one chunk'] = {
  fn: async function(deferred) {

conartist6

const item = {
  done: true,
  value: null,
};

function* wrap(source) {
  try {
    yield* source;
  } catch (e) {
    // this never happens

conartist6

/* @macrome
 * @generated-by ./index.js
 */
const React = require('react');

const styles = require('index.module.css.js');
require('index.module.css');
// The bundler needs a css require to exist for static analysis.
// Node require hooks may be used to make requiring any .css a no-op.

conartist6

I'm working on a brand new build system, and I want to take a moment to address the obvious question, which is: OMGWTFBBQ why another one!?

The answer is in the trees.

The new tool, Macromé (pronounced "macro-may", imported as macrome) is powerful becase it performs in–place builds within existing directory tree structures, so that many types of data about the same underlying unit stay colocated.

For example a React component expressed as a tree-structured directory (a.k.a pod, or unit) and built by macrome might look like this:

[projectRoot]

conartist6

const matching = {
  '{': '}',
  '}': '{',
};

export const tokenize = (lexEngine) => {
  const { start, get, take, end, setType } = lexEngine; // token fns
  const { peekChar, pushState, popState, match, matchable, allMatched } = lexEngine;

  const literal = (n) => {

conartist6

function swap(arr, aIdx, bIdx) {
  if (aIdx < 0 || aIdx >= arr.length) throw new TypeError();
  if (bIdx < 0 || bIdx >= arr.length) throw new TypeError();

  const temp = arr[aIdx];
  arr[aIdx] = arr[bIdx];
  arr[bIdx] = temp;
}

function shiftToEnd(arr, idx) {