move ts-node to devDependencies

[vorant94]

move ts-node to devDependencies

[cristiand391]

hey, sorry missed the last response.

AFAIK, npm installs peerDependencies by default unless you do npm i --omit peer:
npm v7 announcement

Maybe we could remove ts-node from @oclif/core as dep and require plugins to have it as a devDep (which already do for bin/dev to work), but that would be a breaking change and might require some refactor to lazy-load ts-node code in core.

[cristiand391]

Hi @vorant94

ts-node is also used to compile TS plugins at runtime when they are linked, see:
#650

plugin/command loading is done in @oclif/core so it needs ts-node as a dep.

[vorant94]

Hi @vorant94

ts-node is also used to compile TS plugins at runtime when they are linked, see:

#650

plugin/command loading is done in @oclif/core so it needs ts-node as a dep.

Is it acceptable to maybe make it a deepDep then?

[cristiand391]

Is it acceptable to maybe make it a deepDep then?

You mean making ts-node a peerDependency?

[vorant94]

Is it acceptable to maybe make it a deepDep then?

You mean making ts-node a peerDependency?

yeah, sorry for typo

[SuperchupuDev]

any updates on this issue? it's a bit annoying to have ts-node always installed when it doesn't get used by any of my dependencies

[git2gus]

This issue has been linked to a new work item: W-14179298

[mdonnalley]

Closed by #794