How to avoid typescript inside the bundle

[manoraj]

Hi,

We are using a bundling strategy in our CLI. With all the commands, the size of the bundle is around 4.3MB. We have noticed that the bundle includes a typescript which is 3.3MB. Excluding this from the bundle will give us great startup improvements.

Question:

1. Does @oclif/core need a typescript package for bundling strategy? If yes, why?
2. Can we disable it?

[mdonnalley]

@manoraj @oclif/core doesn't list typescript as a dependency in any way. In fact, we have a test that ensures it's never included

My guess is that it's being included in your bundle because of this line. That code is meant to support auto-compiling a plugin in an development environment - the assumption is that typescript will be a devDependency of the plugin you're developing. If it can't find typescript, it'll bypass the auto-compilation step and use whatever compiled source is available to run.

Based on that, I would configure your bundler to skip or remove typescript from the bundle (I'm assuming that's possible - I don't have a lot of experience bundling). Your CLI will be able to operate just fine without typescript in the bundle

[manoraj]

Hi @mdonnalley Thanks for the clarification. Let me check this and get back with my findings