Per web specifications the HTTPS imports PR has import.meta.url values that do not correspond to the cache key; Likely, it should be possible to make this intercept-able and recreate-able via Loaders which is not possible currently.

The future (and hopefully very near future) way to achieve performative module script loading will likely come in the form of implementing “worklet infrastructure” in core since it does not seem like a userland solution should be reasonably expected.

Worklets are a piece of specification infrastructure which can be used for running scripts independent of the main JavaScript execution environment, while not requiring any particular implementation model. — https://html.spec.whatwg.org/multipage/worklets.html

This issue should help us track progress in this area, which I find to be of great interest.

Fixed an error caused by using the incorrect filesystem function.

Fixes #3

Hello, i have error in your same code:

const fs = require('fs');

// The whole library exposes just a single function: const generateID3Segment = require('id3-ts-lib');

// If a PID is falsey, then that track will not be included in the generated PMT const options = { pmtPid: 0x100, id3Pid: 0x103, videoPid: null, audioPid: null, id3PTS: 282743, data: 'This is just some example payload...', };

// The function returns a promise that resolves to a buffer generateID3Segment(options).then((segment) => { fs.writeSync('test.ts', segment); });

Return this error.

(node:1776) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_ARG_TYPE]: The "fd" argument must be of type number. Received type string at Object.writeSync (fs.js:552:3) at generateID3Segment.then (/root/id3/id3.js:18:6) at process._tickCallback (internal/process/next_tick.js:68:7) at Function.Module.runMain (internal/modules/cjs/loader.js:834:11) at startup (internal/bootstrap/node.js:283:19) at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3) (node:1776) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:1776) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

is this an error in the sample code? or in your library?

Fixed an error caused by using the incorrect filesystem function.

Fixes #3

BTW, I did a quick search and came up with the following. (not 100% sure but It'll help some) And I found some cases to receive some none-string values. so I'll post it here for future reference.

• ERR_INPUT_TYPE_NOT_ALLOWED
  • doesn't receive any arguments.
• ERR_INVALID_ARG_VALUE
  • receives an unknown value.
  • If the value of conditions, which supposed to be a string array, ISN'T string array, It receives the conditions as args.
• ERR_INVALID_MODULE_SPECIFIER
  • string only
• ERR_INVALID_PACKAGE_CONFIG
  • Almost string only. Possibly receives a boolean value false, But It's not a huge problem I think.
• ERR_INVALID_PACKAGE_TARGET
  • Almost string only. Possibly receives a boolean value false.
• ERR_MANIFEST_DEPENDENCY_MISSING
  • string only
• ERR_MODULE_NOT_FOUND
  • string only
• ERR_PACKAGE_IMPORT_NOT_DEFINED
  • Almost string only. Not sure but possibly receives a some kind of falsy value if packageJSONUrl is falsy. It looks like packageJSONUrl can be falsy only when it's undefined I guess. (not sure I may be wrong)
• ERR_PACKAGE_PATH_NOT_EXPORTED
  • string only
• ERR_UNSUPPORTED_DIR_IMPORT
  • string only
• ERR_UNSUPPORTED_ESM_URL_SCHEME
  • Receives URL object. Well, I guess it might be cryptic. 🤔

Thanks. :)

Here's what it looks like. (And that's what I expected.)

$ node --loader=ts-node/esm foo.ts
(node:4352) ExperimentalWarning: --experimental-loader is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)

/home/naoki/workspace/ts-node/dist-raw/node-esm-resolve-implementation.js:383
    throw new ERR_MODULE_NOT_FOUND(
          ^
Error: Cannot find module '/home/naoki/workspace/ts-node/foo.ts' imported from /home/naoki/workspace/ts-node/
    at finalizeResolution (/home/naoki/workspace/ts-node/dist-raw/node-esm-resolve-implementation.js:383:11)
    at moduleResolve (/home/naoki/workspace/ts-node/dist-raw/node-esm-resolve-implementation.js:818:10)
    at Object.defaultResolve (/home/naoki/workspace/ts-node/dist-raw/node-esm-resolve-implementation.js:929:11)
    at /home/naoki/workspace/ts-node/src/esm.ts:67:38
    at Generator.next (<anonymous>)
    at /home/naoki/workspace/ts-node/dist/esm.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/home/naoki/workspace/ts-node/dist/esm.js:4:12)
    at resolve (/home/naoki/workspace/ts-node/dist/esm.js:31:16)
    at Loader.resolve (internal/modules/esm/loader.js:88:40)

I left those other error types original behavior as it is. So actually, I haven't checked that far. Well, I'll check it out anyway. 👍