jfparadis/tape-xs

tape-xs: tape work-alike for xs

One of main differences between node.js and the Moddable XS SDK is modules: xs supports only ES6 modules. Attempting to port tape showed extensive CommonJS dependencies. Incremental development of a work-alike has worked reasonably well so far.

A typical usage of tape is npm test where package.json has...

{
  "name": "@agoric/eventual-send",
  "scripts": {
    "test": "tape -r esm 'test/**/test*.js'",
  }
}

To run these tests using the Moddable XS SDK, we make a manifest and a main module:

agoric-sdk/packages/eventual-send$ node -r esm .../tape-xs/bin/tape-xs-build.js $(pwd)/ test/test*.js
{ manifest: 'test-xs-manifest.json', main: 'test-xs-main.js' }
try: mcconfig -d -m test-xs-manifest.json

Then we use mcconfig -p x-cli-lin -d -m test-xs-manifest.json to build a test runner, $MODDABLE/build/bin/lin/release/eventual-send. The output of the test runner looks like:

in eventual-send driver...
running test/test-e...
running test/test-hp...
running test/test...
...
ok 3 should be equal
ok 4 should be equal
Result:
{"pass":42,"fail":0,"total":42}

Moddable SDK refinements: x-cli-lin platform

As of this writing, we use a version of the Moddable SDK refined with a CLI-oriented main loop:

https://github.com/dckc/moddable/releases/download/ag08/moddable-linux-sdk.tgz https://github.com/dckc/moddable/releases/tag/ag08 ff41561

The normal Moddable simulator and debug LOG window may or may not work.

Limitations: fragile module manifest approach

Building the module map is likely to be fragile.

The xs manifest format is insensitive to the path where a module specifier is found. Where in node.js ./E would refer to one thing in lib1/m1.js and another in lib2/m2.js, it can only refer to one thing in xs.

See struggling with ../.. in import specifier paths #57.

Limitations: incremental port of tape API

The tape API is ported incrementally as I run into methods that are used in Agoric tests. It is unlikely to be complete.

Issues: @agoric/harden

On xs, @agoric/harden fails a runtime assertion, so we use a different approach. See src/harden-xs.js for details.