@oclif/core 2.x ts-node is not register in local

[kerm1it]

I used version 1.x before, and now I have updated to version 2.x (we also need to support node 16, so we can't update to the latest version)

In version 1.x, I can directly modify src/commands/a.ts to take effect directly, but in 2.x, I need to execute build first before it can take effect

After investigation, I found that:

In version 1.x, the file in src/commands is automatically read in the local development environment

In version 2.x, the file in lib/commands is read

I use yarn link locally to link the command to the global environment, hoping that the files under src can be automatically read when developing locally.

[mdonnalley]

@kerm1it being that v2 is 2 majors behind there's not much I can do to resolve the issue. But I do have a couple of suggestions

• Enable the DEBUG=* environment variable. The logs for the ts-node logic are much better in the latest major but there still might be some helpful information there about what oclif/core is attempting to do with ts-node
• Do you have ts-node list as a dev dependency in your project?
• Is your plugin ESM? If so, auto-compilation won't work