Awesome, thanks!

Yes, everything is built manually.

Is there a way to test it? Manually, or in an automated way.

Is there a way to test it? Manually, or in an automated way.

I've been testing it by manually modifying the tests mostly, I didn't want to be too invasive and changing the whole testsuite. For example this for a hash test:

import nacl from './nacl-fast.mjs';
import util from 'tweetnacl-util';
import test from 'tape';
nacl.util = util;

var enc = nacl.util.encodeBase64,
    dec = nacl.util.decodeBase64;

let randomVectors = /* insert/import ./data/hash.random.js here */

test('nacl.hash random test vectors', function(t) {
  randomVectors.forEach(function(vec) {
    var msg = dec(vec[0]);
    var goodHash = dec(vec[1]);
    var hash = nacl.hash(msg);
    t.equal(enc(hash), enc(goodHash));
  });
  t.end();
});

I think the problem is how to keep CommonJS compatability while still running tests on ESM files, especially when tests themselves include certain dependencies. One solution would be to build separate versions and then run tests against those, but that sort of defeats the purpose of having native modules.

Please let me know if you have an idea on how I can keep compatibility but still test ESM though, that'd be great :)

Thanks, I'll figure something out for testing.

Any progress?

Closing since this is probably not getting merged and there are probably better (but also more invasive) ways to do it.

Thank you very much for your changes - although they did not make it into the original code, they still allowed me to make tweet-nacl.js ESM compatible in my own fork within a few minutes!

@rozek No problem, nice to see somebody using it! Seems like there are a couple of different forks that have done this now, maybe list yours also on #170.