ts-node-esm binary which spawns a subprocess with --loader ts-node/esm #1258

Activity

1. cspotcode

   added

   researchNeeds design work, investigation, or prototyping. Implementation uncertain.Needs design work, investigation, or prototyping. Implementation uncertain.

   on Mar 1, 2021
2. cspotcode commented on May 23, 2021

   

   cspotcode

   on May 23, 2021

   CollaboratorAuthor

   More actions

   Documentation:

   Should state that this feature exists solely to support esm use-cases. If spawning a child process is no longer necessary in the future because node adds an API for setting loaders, then this flag will stop spawning a child process.

   Implementation ideas:

   Parent process loads config, going only as far as is necessary to see that you specified "esm"

   • skip loading typescript & tsconfig.json if --esm already specified via CLI

   Then it spawns a child process, setting env var TS_NODE_CHILD_ARGS=<base64encodedJSON> and NODE_OPTIONS="--loader ts-node/esm"

   Child process detects TS_NODE_CHILD_ARGS, parses it, and immediately unsets it
   Child continues config loading where parent left off
   Child establishes both ESM and CJS hooks

   • Will entrypoint need to be resolved to absolute path before spawning child?
     • Is this resolution affected by config at all? hopefully not
     • Can we hack it since we're installed as a resolver? Replace it with ts-node-child:129365798 and detect that ID in our resolver?
3. cspotcode commented on Jan 27, 2022

   

   cspotcode

   on Jan 27, 2022

   Last edited by cspotcode

   CollaboratorAuthor

   More actions

   Had an idea for suppressing the "experimental" warning from node. node's default warning logger is an event handler on the process 'warning' event.

   When we launch the subprocess, we can pass -r ./suppress-warnings.cjs

   It can do:

   // Not shown here: Additional logic to correctly interact with process's events, either using this direct manipulation, or via the API
   const warningEvent = process._events.warning;
   // TODO validate that this looks like node's built-in warning handler
   // TODO validate that this is not undefined, which might be caused by `--no-warnings`
   const messageMatch = /--(?:experimental-)?loader\b/;
   process._events.warning = function(warning, ...rest) {
     if(warning.name === 'ExperimentalWarning' && messageMatch.test(warning.message)) return;
     return warningEvent.call(this, warning, ...rest);
   });
4. cspotcode

   added this to the 10.6.0 or 10.5.1 milestone on Feb 22, 2022
5. cspotcode

   modified the milestones: 10.6.0, 10.7.0 on Mar 1, 2022
6. cspotcode

   closed this as completedin #1655on Mar 5, 2022
7. crapStone

   added a commit that references this issue on Mar 8, 2022

   Update dependency ts-node to v10.7.0 (#1200)

   ...

   8176da9