Installing as dependency (instead of devDependency) makes final bundle big

[elledienne]

I noticed that this library lists typescript as a peer dependency in the package.json. At the same time, the README suggests installing this library by doing npm install schema-dts.

What happens then is that when I generate the bundle for my server, this library and also typescript are being bundled together with my server code, making the bundle quite big (typescript alone is 3MB minified).

Am I doing something wrong? Or should this library be installed as a devDependency instead?

[Eyas]

Hm, great point.

If you use import {...} from 'schema-dts';, your bundler might not optimize away that import, so you might still need the empty index.js that comes with schema-dts. If you use import type {...} from 'schema-dts';, then you can probably just install it as a dev dependency.

I think removing typescript as a peer dependency is probably right, to allow folks to use this library however way they like without being too restrictive about bundling/optimizing. The side-effect being that without typescript in your development toolchain, this library isn't helpful at all.

[guy-borderless]

This change is required to use schema-dts in a serverless setting like deno-deploy, since including the 38MB of typescript makes the bundle size prohibitive. Any update on when this will be released?

[Eyas]

Fixed in v1.1.5, sorry for delay

[guy-borderless]

Fixed in v1.1.5, sorry for delay

Thank you for doing open source for us!

[thernstig]

@Eyas is there a rationale to not update the README to show:

npm install  --save-dev schema-dts

TypeScript definitions are only needed during development here.

[Eyas]

Hi @thernstig -- the rationale is mostly for historical reasons, when we used real TypeScript enums so it wasn't just pure types. I agree --save-dev is a good call here. Happy to accept a contribution!

[thernstig]

@Eyas sure I can contribute! Can you re-open?

[Eyas]

Sure