guybedford

JSPM Project Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”), and conveys certain license rights to Guy Bedford, 309-3277 Quadra Street, Victoria BC, V8X 4W9  (“Assignee”) for Your contributions to JSPM open source projects. This Agreement is effective as of the latest signature date below.
1. Definitions.
“Code” means the computer software code, whether in human-readable or machine-executable form, that is delivered by You to Assignee under this Agreement. 
“Project” means any of the projects owned by Assignee including both commercial and open source works and including all projects distributed under the JSPM project organization account on GitHub.
“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any Project, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the

guybedford

Keybase proof

I hereby claim:

• I am guybedford on github.
• I am guybedford (https://keybase.io/guybedford) on keybase.
• I have a public key ASC0rq68wlYMNf-xXCQat7dKCBoSIMpQtcOBYpEfwBI7Zwo

To claim this, I am signing this object:

guybedford

[
  "@-ui/react",
  "@-ui/styles",
  "@acies/core",
  "@adobe/leonardo-contrast-colors",
  "@aduh95/viz.js",
  "@advertising-all/advertising-homepage",
  "@agoric/harden",
  "@agoric/make-hardener",
  "@ajmey/toaster",

guybedford

const mocks = Object.create(null);
global.mock = function (_mocks) {
  Object.assign(mocks, _mocks);
};

export async function resolve (specifier, context, parentResolve) {
  if (mocks[specifier]) {
    return { url: 'mock:' + specifier };
  }
  return parentResolve(specifier, context);

guybedford

Current PR: nodejs/node#27850

Initial Discussion of Concerns: nodejs/node#27850 (comment), WebAssembly/esm-integration#30

Summary

Node.js is looking to release support for WASI module imports through --experimental-wasi-modules.

There are three main components to this integration:

guybedford

/*
 * Adapted from node-ecstatic by Joshua Holbrook:
 * https://github.com/jfhbrook/node-ecstatic/tree/master/lib/ecstatic/show-dir
 */

const fs = require('graceful-fs');
const path = require('path');
const he = require('he');

const perms = ['---', '--x', '-w-', '-wx', 'r--', 'r-x', 'rw-', 'rwx'];

guybedford

// meta, packages deep
function getSharedProperties(configA, configB) {
  var bKeys = Object.keys(configB);
  return Object.keys(configA).filter(function(p) {
    return bKeys.indexOf(p) != -1;
  });
}

function detectMetaConflict(metaA, metaB) {

guybedford

Question - should import {fs} from 'fs' be supported for CommonJS module loading from ES6?

If it is to be supported, we would effectively define the fs module object in the ES6 registry to look something like the following:

var fs = require('fs');
var _fs = {};
Object.keys(fs).forEach((p) => _fs[p] = fs[p]);
_fs.default = fs;

guybedford

var firstTree, secondTree;

builder.trace('app/first', config)
.then(function(trace) {
  firstTree = trace.tree;
  return builder.trace('app/second');
})
.then(function(trace) {
  secondTree = trace.tree;
  return builder.subtractTrees(firstTree, secondTree);

guybedford

// our side table
// registry = { deps, declare ; normalizedDeps, depMap ; execute, exports }
// Lifecycle:
// 1. before instantiate, just deps, declare
// 2. after instantiate, normalizedDeps and depMap
// 3. after linking, execute, exports
// 4. after partial tree execution just exports
// 5. after full tree execution, removed from registry
var registry = {};