Skip to content

feat: path to a custom tsconfig #716

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 28, 2022
Merged

feat: path to a custom tsconfig #716

merged 1 commit into from
Mar 28, 2022

Conversation

threepointone
Copy link
Contributor

This adds a config field and a command line arg tsconfig for passing a path to a custom typescript configuration file. We don't do any typechecking, but we do pass it along to our build process so things like compilerOptions.paths get resolved correctly.

@changeset-bot
Copy link

changeset-bot bot commented Mar 28, 2022

🦋 Changeset detected

Latest commit: 03d9664

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

This PR includes changesets to release 1 package
Name Type
wrangler Patch

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
Copy link
Contributor

github-actions bot commented Mar 28, 2022

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.developers.workers.dev/runs/2052312105/npm-package-wrangler-716

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.developers.workers.dev/prs/716/npm-package-wrangler-716

Or you can use npx with this latest build directly:

npx https://prerelease-registry.developers.workers.dev/runs/2052312105/npm-package-wrangler-716 dev path/to/script.js

This adds a config field and a command line arg `tsconfig` for passing a path to a custom typescript configuration file. We don't do any typechecking, but we do pass it along to our build process so things like `compilerOptions.paths` get resolved correctly.
Copy link
Contributor

@petebacondarwin petebacondarwin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If no custom config is provided, do we default to a tsconfig.json in the project root?
If not, then would we need to provide a config option for that if we wanted it?

@threepointone
Copy link
Contributor Author

esbuild has its own machinery for finding then nearest tsconfig (which iiuc follows the same algo that typescript itself does) so I don't think we should do anything different here.

@threepointone threepointone merged commit 6987cf3 into main Mar 28, 2022
@threepointone threepointone deleted the custom-tsconfig branch March 28, 2022 15:14
@github-actions github-actions bot mentioned this pull request Mar 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants