Custom tsconfig path for the build command

[enisdenjo]

The tsconfig.json file is implicitly read to inherit tsc options during the build phase.

However, sometimes you might have multiple config files and use one for build. One common reason is one tsconfig checks the types of all files (including other configs and tests) and another tsconfig specifies what is to be built.

This PR allows for a --tsconfig option to directly specify the tsconfig to use.

TODO

• Tests

[changeset-bot]

🦋 Changeset detected

Latest commit: d7c4ed6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
bob-the-bundler	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package	Version	Info
bob-the-bundler	5.1.0-alpha-20230126161914-54dd016	npm ↗︎ unpkg ↗︎

[enisdenjo]

Do you guys think b508a86 should be flagged a breaking change?

[n1ru4l]

Not sure why we should do tsconfig.build.json by default. I like to keep things simple and having multiple tsconfigs should be avoided. I don't care about a slightly longer build time because of test type checking - wouldn't we solve it anyways with the incremental flag?

[enisdenjo]

The idea is to keep bob opinionated and thereby speed up the necessary setup, would require less arguments with tsconfig.build.json as the default.

[enisdenjo]

Re-opened in #202.