Move typescript to dev dependencies

[coopbri]

Description

During the bootstrapping process of @vendure/create, the typescript package is installed as a regular dependency, I moved it to the dev dependencies.

Regarding dotenv, it appears it's only used in the CLI, dev server, and in E2E tests for the payments plugin, please let me know if I missed something and it should be kept as a prod dep.

Breaking changes

No

Screenshots

N/A

Checklist

• I have set a clear title
• My PR is small and contains a single feature
• I have checked my own PR

[netlify]

✅ Deploy Preview for effervescent-donut-4977b2 ready!

Name	Link
🔨 Latest commit	aebde9e
🔍 Latest deploy log	https://app.netlify.com/sites/effervescent-donut-4977b2/deploys/663b1b21e4e91c00087f0540
😎 Deploy Preview	https://deploy-preview-2816--effervescent-donut-4977b2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[michaelbromley]

Hi,

The reason that dotenv is a regular dependency is that in the vendure-config.ts file, it is used to automatically load env vars which are used in the config. Moving it to a dev dependency would require a change to how env vars are handled there.

I think moving typescript to a devDependency is fine though. I can't off the top of my head think of why that would be an issue.

[coopbri]

Hi,

The reason that dotenv is a regular dependency is that in the vendure-config.ts file, it is used to automatically load env vars which are used in the config. Moving it to a dev dependency would require a change to how env vars are handled there.

I think moving typescript to a devDependency is fine though. I can't off the top of my head think of why that would be an issue.

Revised!