Breaks dependencies in mono repos when using yarn

If I install my dependencies with yarn install --frozen-lockfile --production and ts-node is only part of my dev dependencies, ts-patch will run npm, not yarn, and destroy my mono repo node_modules.

Desired fix:

• please use yarn when there’s a yarn.lock
• alternatively; add an option to skip npm usage, and either throw a warning or an error when mismatch dependencies.

My workaround currently:

• moved ts-node to dependencies

[manuth]

Awesome! Thanks for the explanation 😄

[nonara]

I thought of something like a remark that you have to install ts-node in the Setup-section of your readme:

I considered it, but ts-node is not actually required to use ts-patch. The majority of people won’t need it to be installed, as they are using transformer packages, which are already compiled to js.

ts-node is only really necessary if you want to try to directly use a .ts transformer. In that case, it should be assumed that ts-node is necessary, but we also throw a pretty clear error message, so I think we’re covered.

https://github.com/nonara/ts-patch/blob/541df51364cf277d003e3ab892ee8a3a2ec5a30f/src/patch/lib/plugin.ts#L163-L169

That said, in v2, it will come pre-packaged, so there won’t be any error.