Export function of child_process

[minkimcello]

Motivation

This comment.

Approach

I think I may be underestimating/misunderstanding the issue but can't we just do:

// > packages/node/src/index.ts

export * as ChildProcess from './child_process';

This seems to allow us to:

import { ChildProcess } from `@effection/node`;

export function * echo() {
  yield ChildProcess.fork("echo", ["Hello World"]);
}

Not knowing how effection works I'm not sure how I can test to make sure it doesn't conflict with @effection's fork but hovering over the imported functions seems to display the intended result:

[cowboyd]

What about the other forms?

import { spawn } from `@effection/node/child_process`

import * as ChildProcess from `@effection/node/child_process`

[minkimcello]

@cowboyd I believe both of those forms work if you specify the dist directory in that path.

// > node/src/index.ts
export { spawn, fork } from './child_process';

☝️ Was this conflicting with fork from @effection?
Because when it's exported and I import it as:

import { fork, spawn } from '@effection/node';

It looks to be importing the correct function.

[cowboyd]

I believe both of those forms work if you specify the dist directory in that path.

Is there a way to do it without having to put dist/ in the middle?

[minkimcello]

@cowboyd Went down a bit of a rabbit hole and found these issues: #10866, #26722, and #33079. I think these people are mentioning what it is that we want to do with @effection/node/child_process.

Could we use something like module-alias?

[cowboyd]

Based on the last ticket, It seems like for node > 13 we can use package exports coupled with tsconfig paths. But maybe we can add that later?

We got burned with module-alias before so not keen to go down that road,

[cowboyd]

@minkimcello Thanks for going down these rabbit holes, otherwise known as "research." This is exactly the information that we need.